
JessicaW.61208 (Customer) さんが質問をしました。
The use case is that the user logs into application A and then needs to access application B. When logging into application A with Okta as the authentication mechanism, application A receives both an access token and refresh token.
When the user when using application A then needs to leverage the capabilities of a SaaS vendor, we'll call application B, a Single use token (SUT) is passed along to application B. If the user's session in application B is longer in duration than the lifetime of the SUT, then is there a way to extend the user's token (using OIDC workflows) that DOES NOT require the user to login again?

Thank you for reaching Okta Support. My name is Tomas and I'll be assisting.
The configuration you are trying to achieve is not possible at the moment as we cannot receive the we cannot receive the token without the user authenticating to an application.
Also is not possible to make the user get the access token and the refresh token from application A and use those to call the application B.