You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Custom OTP Authenticator SPI, without browser involvement
#21166
I'm trying to develop a custom authenticator, which will be triggered from a backend service (whatsapp channel) without browser involvement. I've managed to hit the authenticate method when I call the openid token endpoint. Which I think I should generate and send the OTP and possibly put some data to the session. But I'm failing to do the next step, which is to hit the action method with the otp value. Reading the following doc:
I tried to call /realms/{realm}/login-actions/authenticate?code={session-code}&execution={executionId} which logs cookie_not_found. I've checked the code for this resource and it says URL called after login page. YOU SHOULD NEVER INVOKE THIS DIRECTLY! :)
I've also tried generating action token and calling /realms/{realm}/login-actions/action-token with all the required parameters, that returns page expired.
Feels like I'm doing something completely wrong. Any help is welcome.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I'm trying to develop a custom authenticator, which will be triggered from a backend service (whatsapp channel) without browser involvement. I've managed to hit the
authenticatemethod when I call the openid token endpoint. Which I think I should generate and send the OTP and possibly put some data to the session. But I'm failing to do the next step, which is to hit theactionmethod with the otp value. Reading the following doc:I tried to call
/realms/{realm}/login-actions/authenticate?code={session-code}&execution={executionId}which logs cookie_not_found. I've checked the code for this resource and it saysURL called after login page. YOU SHOULD NEVER INVOKE THIS DIRECTLY!:)I've also tried generating action token and calling
/realms/{realm}/login-actions/action-tokenwith all the required parameters, that returns page expired.Feels like I'm doing something completely wrong. Any help is welcome.
All reactions