|
|
|
|
|
by Kletiom
1568 days ago
|
|
Puh the article has the same problem as auth always has: lots and lots of magic words which are hard to remember what one word exactly means. We just use keycloak everywhere and I don't know if our setup uses oauth, sso, jwt,oauth2, open id, saml etc. Keycloak library works, configuring Google as an additional provider is easy. I trust that setup but it would be great if we would just have one thing with x features and everyone supports it. You want to connect Fe with be? Use a. You need API token/auth, use b. You want to allow auth from ext? Use c. What I will not do though, auth as a service. I add Google and co because the customer is thrusting them. |
|