Skip to content

Commit ad0786a

Browse files
Update 2020-08-26-auth.md
1 parent 0cca515 commit ad0786a

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

blog/2020-08-26-auth.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,12 +26,11 @@ You may manage this by having a neat notebook with a 100 credentials or you may
2626

2727
## Single Sign On
2828

29-
3029
If a single Passport can work regardless of which country is being visited, why do separate government applications require separate login credentials? A single set of credentials should be sufficient to authenticate one’s digital identity regardless of which application one is trying to sign in to: registering for a new driver’s license or paying one’s advance tax. This is what is often referred to as a “Single Sign On” (SSO) capability.
3130

3231
Implementing this within a set of existing, deployed applications is possible if user identities are managed independently: think of it as needing only a single set of credentials to sign in to multiple bank account applications. Instead of the user identities – your name, bank account number – living inside each separate application, they are removed and managed centrally by a separate component, which manages your registrations to each application, and the required metadata linked with each.
3332

34-
![](https://samagra-development.github.io/docs/img/blog-auth.png)
33+
![](https://samagra-development.github.io/docs/img/blogauth.png)
3534

3635

3736
## Authorisation: Access Control Lists

0 commit comments

Comments
 (0)