guys? They have most complex deployment out
there.
As fair as other JBoss projects go and allowing them to embed Keycloak into their
projects, this is along the lines of what I proposed. Although this is proposing to change
the behaviour of Keycloak not just remove features.
For other users I don't see the use-case. We should instead focus on making sure
Keycloak has the required features and is easy to use.
----- Original Message -----
From: "Bill Burke" <bburke(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Monday, February 23, 2015 5:28:10 PM
Subject: [keycloak-dev] Simple mode?
Conversations with
jboss.org guys got me thinking. Should we have a
"simple mode" for Keycloak where there is no concept of a client,
application, or roles? In this case,
* applications don't need session mgmt or single log out
* All applications are hosted under the same domain i.e *.jboss.org
(
issues.jboss.org,
forums.jboss.org, etc...)
* applications just need to know if 1) the user is logged in, 2) the
username/id
So, "simple mode" would be:
* No applications/client panel
* No role pages anywhere
* Realm would have a global javascript referable cookie that contained
basic information (userid, username, full name). The domain and path
would be configurable from admin console
* Realm would have a list of valid redirect URI patterns.
* Realm would have a default redirect page for unsolicited logins.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev