Content
Activity
12/06/2024
-
updated by
Jan Sandbrink on 12/06/2024 05:09 PM -
Comment added
One more thought from my side: We have a pretty huge amount of optionality around this. For this feature to work as inte...
- Description changed (Details)
-
Comment added
-
updated by
Jan Sandbrink on 12/06/2024 04:52 PM - Status changed from in development to needs review
- Assignee deleted (
Jan Sandbrink)
-
updated by
GitHub on 12/06/2024 04:28 PM - Comment added
-
updated by
Jan Sandbrink on 12/06/2024 03:20 PM - Status changed from in development to needs review
- Assignee deleted (
Jan Sandbrink)
-
updated by
GitHub on 12/06/2024 03:14 PM - Comment added
-
updated by
Jan Sandbrink on 12/06/2024 11:50 AM - Status changed from confirmed to in development
-
updated by
Jan Sandbrink on 12/06/2024 11:47 AM - Assignee set to Jan Sandbrink
-
updated by
Dominic Bräunlein on 12/06/2024 11:37 AM - Status changed from new to confirmed
- Assignee set to Jan Sandbrink
- Developers set to OP Dev Titan Team
-
created by
Jan Sandbrink on 12/06/2024 10:47 AM -
updated by
Oliver Günther on 12/06/2024 08:59 AM -
Comment added
As long as the behavior is not clear, I'm also for rejecting this. It would be nice to reject values filled from the pro...
- Status changed from needs clarification to rejected
-
Comment added
-
updated by
Jan Sandbrink on 12/06/2024 08:36 AM -
Comment added
Dominic Bräunlein Perfect. This is what I had in mind while browsing the code right now as well.
My proposal right now w...
- Subject changed from Add OIDC provider type "Keycloak" to Store token exchange capability on OIDC providers
- Description changed (Details)
- Status changed from needs review to in development
-
Comment added
-
updated by
Dominic Bräunlein on 12/06/2024 08:30 AM -
Comment added
Jan Sandbrink Good point.
It makes sense that we focus on the token exchange capabilities instead. When an admin sets up...
-
Comment added
-
updated by
Jan Sandbrink on 12/06/2024 08:15 AM -
Comment added
Starting to understand that this feature is intended as a way to recognize Providers compatible with Token Exchange (see...
-
Comment added
-
updated by
Jan Sandbrink on 12/06/2024 08:13 AM -
Comment added
I agree to what Wieland said regarding this not being Keycloak-specific.
Can we check that the provider offers the toke...
-
Comment added
12/05/2024
-
updated by
Jan Sandbrink on 12/05/2024 05:36 PM - Status changed from in development to needs review
- Assignee deleted (
Jan Sandbrink)
-
updated by
GitHub on 12/05/2024 05:35 PM - Comment added
-
updated by
Jan Sandbrink on 12/05/2024 05:14 PM -
Comment added
Dominic Bräunlein I think I'll be able to provide a PR for this soon.
Are we planning to use the Keycloak provider type ...
- Status changed from specified to in development
- Assignee set to Jan Sandbrink
- Accountable set to Jan Sandbrink
-
Comment added
-
updated by
Jan Sandbrink on 12/05/2024 01:22 PM -
Comment added
I am inclined to reject this bug or at least want to clarify desired behaviour.
As far as I can tell, this was introduce...
- Status changed from confirmed to needs clarification
-
Comment added
12/04/2024
-
updated by
Wieland Lindenthal on 12/04/2024 11:13 AM - The changes were retracted.
-
updated by
Dominic Bräunlein on 12/04/2024 08:08 AM - Status changed from in development to on hold
Also available in: Atom