Yuriy,
I have question that I've been trying to answer by reading your source code, but I don't want to leave this ticket hanging so I'll just share it here:
Regarding step 2 of the flow you have presented. Is this redirecting step supposed to be implemented client side or server side? When trying to request a token using the ticket provided by the AM server, I get a 403 Forbidden response containing (example):
```
{
"error": "need_info",
"ticket": "2325659d-4469-4c2a-8b3b-ecc05617f6de",
"required_claims": [
{
"issuer": [
"%1$s"
],
"name": "uid",
"claim_token_format": [
"http://openid.net/specs/openid-connect-core-1_0.html#IDToken"
],
"claim_type": "string",
"friendly_name": "uid"
}
],
"redirect_user": "https://nextgeoss-sso-ref.elecnor-deimos.com/oxauth/restv1/uma/gather_claims"
}
```
Am I supposed to just leverage this redirect client-side like UMA 2.0 suggests?
Thanks, Hector