OAuth 2 Token Introspection

  Рет қаралды 7,878

Jan Goebel

Jan Goebel

Күн бұрын

Пікірлер: 17
@drstrangebudgie4052
@drstrangebudgie4052 5 ай бұрын
Great video. I would also mention that the structured token has an expiration date. So if a token is revoked at the auth server but the resource server doesn't introspect, at least the resource server will only accept the token until it expires anyway.
@АлёнаЧжен-х5п
@АлёнаЧжен-х5п 6 ай бұрын
Perfect video! Only thanks to that I`ve understood why is token introspection sometimes needed with jwt tokens. Thank you very much!
@jgoebel
@jgoebel 6 ай бұрын
Glad it helped!
@nyplace1
@nyplace1 2 жыл бұрын
Excellent video, crystal clear. You have a talent, please keep posting great content.
@jgoebel
@jgoebel 2 жыл бұрын
Thank you so much!
@funfactor4282
@funfactor4282 Жыл бұрын
Nice work. Explaination is wonderful
@jgoebel
@jgoebel Жыл бұрын
Thanks a lot!
@florianwege7563
@florianwege7563 Жыл бұрын
The Authorization Server could also push a notification about the revocation to the resource server or like periodically push a list of all revocations that happened recently (depending on the configured token life span) along with a timestamp, then the resource server could also interpret this as a heartbeat and detect when the messages from the authorization server did not arrive. But yeah, the revocation and possibility of stealth or permission changes is why the access token should be short-lived.
@beratdinckan5585
@beratdinckan5585 2 жыл бұрын
thanks! I just liked and subscribed.
@jgoebel
@jgoebel 2 жыл бұрын
Awesome, thank you!
@Alex-zm9ww
@Alex-zm9ww 2 жыл бұрын
Why this and the previous video are not part of the OAuth playlist?
@jgoebel
@jgoebel 2 жыл бұрын
because i forgot to add them 😅
@kousheralam
@kousheralam Жыл бұрын
For token revocation what if i publish a event to a event bus, with the revoked token hash so that resource server can keep it their local cache for the token lifetime, and reject the token if passs after revocation ? or is there any standard for token revocation ?
@jgoebel
@jgoebel Жыл бұрын
This would only work if the AS and the resource server are from the same entity / company or the AS would give each client a dedicated topic even though f the client is a third party. But in principle yes.
@rickr937
@rickr937 2 жыл бұрын
Could you do more tutorials in nodejs. For instance I would like a production ready backend for the Tinder clones made in react of so many youtubers. They always leave the backend to something like firebase or barely work on the matching algorithm.
@ZiiiP2142
@ZiiiP2142 Жыл бұрын
Thanks.
@jgoebel
@jgoebel Жыл бұрын
You're welcome!
OAuth 2.0 - a dead simple explanation
9:16
Jan Goebel
Рет қаралды 24 М.
OAuth 2.0 Pushed Authorization Requests
9:35
Jan Goebel
Рет қаралды 3,8 М.
Thank you Santa
00:13
Nadir Show
Рет қаралды 37 МЛН
Noodles Eating Challenge, So Magical! So Much Fun#Funnyfamily #Partygames #Funny
00:33
Twin Telepathy Challenge!
00:23
Stokes Twins
Рет қаралды 121 МЛН
Do you love Blackpink?🖤🩷
00:23
Karina
Рет қаралды 21 МЛН
OAuth 2.0 and OpenID Connect (in plain English)
1:02:17
OktaDev
Рет қаралды 1,8 МЛН
Secure Integrations with OAuth 2.0 JWT Bearer Flow
18:36
Salesforce Developers
Рет қаралды 174
Why is JWT popular?
5:14
ByteByteGo
Рет қаралды 338 М.
OAuth 2.0 - Token Exchange
14:34
Sascha Preibisch
Рет қаралды 11 М.
OpenID Connect vs OAuth | OpenID Connect explained
8:50
Jan Goebel
Рет қаралды 40 М.
Difference between cookies, session and tokens
11:53
Valentin Despa
Рет қаралды 657 М.
OAuth explained | OAuth 2.0
8:47
Jan Goebel
Рет қаралды 40 М.
Exploring OAuth 2.0: Must-Know Flows Explained
12:22
Code and Stuff
Рет қаралды 1,3 М.
Thank you Santa
00:13
Nadir Show
Рет қаралды 37 МЛН