Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to automatically get the Key Assertion key from admin page? #299

Closed
SalamanderHP opened this issue Jul 22, 2023 · 2 comments
Closed

Comments

@SalamanderHP
Copy link

SalamanderHP commented Jul 22, 2023

I am struggling to handle this issue because we just can not keep manually creating the user on admin page and then filling it into our system in order to create valid JWT. Do you have any APIs or CLI for that. Hope you guys have a solution for this!

@SalamanderHP SalamanderHP changed the title How to get automatically the Key Assertion key from admin page? How to automatically get the Key Assertion key from admin page? Jul 22, 2023
@BobWall23
Copy link
Member

Why are you creating users on our admin page and filling them into your system?
Our libraries are built so that you manage users in your system and handle authentication there. You create one user in our Admin page and get the assertion key there, then use that assertion key to tell us the identity of the user in your application. You definitely should not be creating a user in the admin console for each user in your system.

@skeet70
Copy link
Member

skeet70 commented Jul 26, 2023

If you haven't seen them already this and this documentation may be useful to help you get an idea of what the pattern is supposed to be and when/how users are created.

We (and others) are also available in our community channels for more conversational help using our libraries. This doesn't appear to be an issue with the ironoxide library.

@skeet70 skeet70 closed this as completed Jul 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants