Enterprise Guide 8.4 and SAS Viya 4 - Authorization Code lifespan

[Technolero]

I have EG 8.4 connected to my Viya 4 2024.06 compute server. To authenticate I generate an authorization code. I haven't really paid attention to how often I need provide a new authorization code. How long does the authorization code last before I have to refresh?

[joeFurbee]

@Technolero,

I don't believe there's an expiration on the auth token; however with any client connection there may be circumstances where the auth token gets rejected. In that case you would have to generate a new auth token and go through the connection process.

[Technolero]

Thanks @joeFurbee. It seems like it prompts me for a code every few days (maybe a week). I will pay more attention and share what I find.

[Wilbram-SAS · Accepted solution]

@Technolero , if I'm not mistaken SAS Enterprise Guide retrieves an Authorization Code and a Refresh Token when you connect the first time to a SAS Viya Compute server. The Authorization Code is used for creating and accessing the Compute server session and is short-lived. When it expires or when a new session needs to be created, EG will use the Refresh Token to request another Authorization Code.

Now regarding validity of these tokens, both can be configured by your SAS administrator:

• Access Token defaults to 1 hour (3600 seconds) - see SAS Viya Platform Administration doc: https://go.documentation.sas.com/doc/en/sasadmincdc/default/calconfigref/n1x8p68cbe5t4jn1ncwlc18q8xd... (oauth2.client - accessTokenValidity)
• Refresh Token defaults to 14 days (1209600 seconds)  - see SAS Viya Platform Administration doc: https://go.documentation.sas.com/doc/en/sasadmincdc/default/calconfigref/n1n7wvetkbf08tn0zlem5s8veml...(oauth2.client - refreshTokenValidity).

[Technolero]

Thank you @Wilbram-SAS ! That was exactly what I was looking for!