BCDevOps / platform-services

Collection of platform related tools and configurations
Apache License 2.0
13 stars 29 forks source link

Enable OTP for a client in KeyCloak 7.3.0.GA #257

Open mitovskaol opened 5 years ago

mitovskaol commented 5 years ago

The Screen Shot 2019-09-18 at 12.41.27 PM.pngScreen Shot 2019-09-18 at 12.41.02 PM.pngScreen Shot 2019-09-18 at 12.40.21 PM.pngAporeto client in DevHub realm in KeyCloak needs to have 2FA enabled for ALL client users

The following steps have been tried (see the screenshots for more details): 1) Create a custom authentication flow with an OTP authentication added as a REQUIRED step. 2) in the Aporeto client specify an Authentication Flow Override to use the custom flow.

We tried different custom flow configuration as seen on the screenshot, but none enforced the OTP authentication. Users were able to get to the protected resource once they successfully authenticated with the identity provider authentication in the step 1 (username/password) and were never prompted for OTP. Making the OTP the first step in the flow did not work either.

Any help with troubleshooting this is greatly appreciated.

mitovskaol commented 5 years ago

Working with RedHat's SSO team on this

ShellyXueHan commented 5 years ago

Updates: unresolved yet

ShellyXueHan commented 5 years ago

Still waiting for feedback from Redhat on OTP feature (https://access.redhat.com/support/cases/#/case/02477238)

ShellyXueHan commented 5 years ago

Update: feature request has been made, but estimation unknown from redhat support It's too late for new features for 7.4 which is planned for Q1 2020, so the next possible time would be RH-SSO 7.5 which isn't currently scheduled. Temporary solution is to stay with GitHub idp for 2fa.