Repository navigation
Direct-Grant Authentication: Supporting X509 Certificate OR Username/Password #45128
Unanswered
Prakhar147
asked this question in
Q&A
Replies: 1 comment 1 reply
|
Also, login works if only the username in provided, even without providing X509 or password which is not expected. Any help is appreciated. |
1 reply
|
Did you find a solution to this. I think you're problem here is that Password isn't required when it should be. However when I do the same you have here, X509 will never validate. |
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.
Hi,
I need to support configuring the direct-grant workflow to support two alternative authentication methods:
Current Configuration:
Created two subflows under the direct-grant authentication flow, both marked as Alternative
Username validation (Required)
Password validation (Alternative)
X509 username validation (Required)
Issue: Despite this configuration, the username validation still appears at the parent level in the subflow diagram. As a result, I cannot authenticate using X509 certificates alone—the system still requires an explicit username input.
Please see the attached screenshot for reference.
Configurations:
Subflow diagram:
Question: Is there a configuration approach that would allow X509 authentication without requiring username input, while maintaining username/password as an alternative method?
All reactions