Skip to content
This repository has been archived by the owner on Sep 21, 2021. It is now read-only.

Cannot register new endpoints #96

Open
elegault opened this issue Jun 18, 2018 · 2 comments
Open

Cannot register new endpoints #96

elegault opened this issue Jun 18, 2018 · 2 comments

Comments

@elegault
Copy link

I've been doing some testing with various endpoints, and it seems the first provider I use for each of Authenticator.endpoints.registerMicrosoftAuth and registerAzureADAuth are "stuck" in storage. Every time I try to register and use a provider with a different client ID, the login is failing and referring to IDs from the first registration attempts. I see the old provider client IDs in storage, but I don't know how to clear them (if it's possible); I've tried Authenticator.endpoints.clear() and they still remain.

So how can I clear the storage and use new providers?

@WrathOfZombies
Copy link
Contributor

@elegault
Copy link
Author

Yes I am. This may not be a bug and perhaps just a symptom of me not understanding how the storage mechanism works. In fact it would be nice if anything about Storage Helpers (and the rest) is documented, as only Authentication has guidance at the moment

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants