Repository navigation
Replies: 2 comments 2 replies
|
I'd strongly prefer the built-in client What you're describing is client metadata/configuration, not authorization for principals, so A pretty common pattern is:
Using roles as a pseudo key-value store tends to make the model harder to reason about later. The fact that the UI does not surface arbitrary attributes especially well doesn't make the underlying attribute map a bad fit for this use case. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I have a question regarding clients and some kind of metadata about these clients:
I try to implement some conditional authentication steps in my authentication flow based on client attributes.
For example, I want to mark all business critical clients in order to perform further checks on the IP, session age and so on.
This could be implemented via a custom condition in the authentication flow and custom authenticators triggered on these conditions.
The problem is: There is no option to add this information to my clients.
At least no option which is fully supported via the UI.
Clients have an
attributesmap in the API, but it's not displayed in the UI.So how do you solve such an issue? How to add custom attributes to a client in order to annotate it for further processing?
I assumed the following options:
Looking forward to your feedback. I'm sure I'm not the only one with this issue, right?
All reactions