You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/11-authentication.livemd
+54Lines changed: 54 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,6 +63,8 @@ Authentication mechanism can be simple or complex. Security industry best pract
63
63
64
64
Tokens are ... long strings of random characters used to identify an entity, session, as a badge for access. Used for authentication, used for session management, provided by authorization servers.
@@ -78,6 +80,58 @@ Base64 encoded and cryptographically signed
78
80
79
81
Tokens, like other authentication credentials, etc. must be protected in transit and at rest.
80
82
83
+
Why use JWT? For post authentication authorization Can be signed and encrypted -> trust; low overhead; Integrity of information being transmited and non-repudiation; JWT checkers validate token; token belongs to user
84
+
85
+
Expiration /Refresh
86
+
87
+
Why use OAuth? when Users need access to third party services, outside of your environment where you don't want to share your credentials with those third parties. In OAuth protocol/architecture, an authorization service brokers access and grants users an access token to present, in place of credentials.
Service X sends Token for limited access to Social Media Account (instead of sharing credentials)
125
+
126
+
https://www.youtube.com/watch?v=996OiexHze0
127
+
128
+
If you're familiar with Kerberos, somewhat similar - three primary entities, requesting, service one, service 2, intermediary server that handles issuing tokens that get presented in lieu of credentials
0 commit comments