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 }}
This repository has been archived by the owner on Jan 26, 2025. It is now read-only.
Within the okta-angular package, the typing output for the Okta Service's .getAccessToken() function return value is declared as any. This causes an issue when attempting to retrieve the access token using the .accessToken property on the object that is returned. After a quick search through the repository, it appears that the reason this is occurring is due to the fact that the return type is missing on the getAccessToken() function definition located on this line of code.
Possible Resolution
Need to define either an interface or a class that will contain the definition for the token than is returned from the @okta/okta-auth-js function definition for then token and set that as the type for the return value of the function. If I get a chance, I will attempt to create this pull request, but please don't count on it.
The text was updated successfully, but these errors were encountered:
Issue:
Within the
okta-angular
package, the typing output for the Okta Service's.getAccessToken()
function return value is declared asany
. This causes an issue when attempting to retrieve the access token using the.accessToken
property on the object that is returned. After a quick search through the repository, it appears that the reason this is occurring is due to the fact that the return type is missing on thegetAccessToken()
function definition located on this line of code.Possible Resolution
Need to define either an interface or a class that will contain the definition for the token than is returned from the @okta/okta-auth-js function definition for then token and set that as the type for the return value of the function. If I get a chance, I will attempt to create this pull request, but please don't count on it.
The text was updated successfully, but these errors were encountered: