Open kicks321 opened 3 years ago
JayNewstrom
commented
3 years ago Hi @Rangyia thanks for the issue. We've not yet added support for the device_sso flow.
Can you tell us more about your use case? Are you using the web redirect, or the custom auth solution?
kicks321
commented
3 years ago Hey @JayNewstromm, we are using the custom auth solution.
From what I'm seeing, the type for the Authentication Response as shown. What would be the expected timeline to get this feature implemented?
JayNewstrom
commented
3 years ago Since this is a new feature (early access and all), we haven't implemented this, or prioritized it on our team.
This SDK has a few transitive dependencies, due to which flow you use (web redirect, or custom auth)
Web Redirect:
Custom Auth:
Our transitive SDKs need to implement support for this feature, before we can add it here. Let me reach out to our PM to figure out next steps.
I'm submitting a:
Bug report
Current behavior
Utilizing the Okta react-native-sdk, has an issue where providing the scope of "devie_sso," the response from the SDK when using "signIn" only provides two things: "access_token" and "resolve_type." The SDK does not provide an initial response of "access_token", "refresh_token", "id_token", and "device_secret". Based on the type for the "AuthroizationResponse", only two types of properties are returned "access_token" and "resolve_type".
Expected behavior
The desired behavior would be that we would like to be able to get additional response attributes from the "sign-in" functionality. We would need the ability to get back "device_secret", "access_token", "response_token", and "id_token" in order to perform the Native SSO Flow provided by Okta.
Minimal reproduction of the problem with instructions
For the client config, add the device_sso option to the scope.
Environment
node -v): 16.9.1