Hell Craig,
Do you mean the user should enter a "partner code" along with login+password?
(either as a 3rd field or in a separate screen)
Or only once during registration / upon the first login?
Cheers,
Dmitry Telegin
CTO, Acutus s.r.o.
Keycloak Consulting and Training
Pod lipami street 339/52, 130 00 Prague 3, Czech Republic
+42 (022) 888-30-71
E-mail: info(a)acutus.pro
On Sat, 2018-11-10 at 09:00 -0600, Craig Setera wrote:
We have an attribute we use to allow customers to to
"scope" or "namespace"
a users interaction with our system (a "partner code" that is known to our
system). In our previous proprietary Java session-based security system,
this value was stored in the Java session at the time of login and used by
the authorization engine to further restrict what the user was allowed to
see.
As we transition to using Keycloak for authentication, I'm wondering if
there is a way to use Keycloak to manage this partner code during a login
session? Some way to send the value during the Keycloak login sequence and
then later retrieve it based on the access token?
Thanks for any insights.
Craig
=================================
*Craig Setera*
*Chief Technology Officer*
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user