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

Question about logout #1

Open
rjpalermo1 opened this issue Jul 16, 2016 · 0 comments
Open

Question about logout #1

rjpalermo1 opened this issue Jul 16, 2016 · 0 comments

Comments

@rjpalermo1
Copy link

First thank you for your time and effort, this is helping me a lot. So what I get is your Authenticate libraries orchestrate. Took me a little time to figure out the workflow but I got it now. What was/is puzzling me is the authenticate-service and how that would look like in say an actual external service. I assume the authentic-service receives a jwt from client then communicates with the authentic-server to access the rsa-private.pem and decrypt the token.

Is this correct?

If so, I assume I can attach a lot of other info in this jwt the client receives like roles (I think it's called scope?) and act on it in my external service.

Is it possible to associate more than email and password when a user registers through the authentic-server? For example, when a user registers to associate other info like normal user profile first name/last name stuff...

Also, I noticed as I was trying this out that after logout the key is destroyed on the client but I can still access the service after using the same key. Is there something I can do on client logout to also restrict that key from being used again on the service?

Thanks again for all you've done David...

media4tech pushed a commit to PMMON4privato/authentic that referenced this issue Nov 24, 2021
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

1 participant