{error: {code: 498, message: "Token Invalid.", ...}

[FarrukhZahid]

HI, 

I am currently using ArcGIS Enterprise 11.4 (Portal-Federated Server) with a developer account subscription. When generating a simple basic API key, I repeatedly encounter a white screen. Checking the network reveals error 498. I have attempted this in different environments, yet the issue persists. Although my environment is secured, I am facing this problem on my local machine (Secured Environment) where the portal is installed. Each time, the key appears as an invalid token.

{
"error": {
"code": 498,
"message": "Token Invalid.",
"details": [
"The required authentication information is invalid. The token is either invalid or has expired."
],

[John-Foster]

@FarrukhZahidan api key generated on ArcGIS Enterprise can only authorize services on that Enterprise instance, so if you are using a key generated on ArcGIS Enterprise to authorize services on ArcGIS Online then you will expect to see error 498 Invalid Token. You will need to log in with an ArcGIS Online account and generate and API key there in order to authorize services from ArcGIS Online.

[TimWestern]

I'm curious, You mentioned a Portal Federated Server (For these dashboards are users logging in through that federation? If so I'm wondering why an APIKey vs an OAuth2 key is preferred here for your purposes.

[John-Foster]

@TimWesternthe use case for the API key would be when the end user does not have an ArcGIS account to authenticate or the app does not want to prompt a user to log in to authenticate access with the services so the api key access token is used. OAuth will require a user to log in to generate the access token.

[TimWestern]

That's a very clear explanation, @John-Foster, Thank you.

[John-Foster]

@DeanWilsoncurrently ArcGIS Experience Builder does not support API key authentication

[TimWestern]

So that means not even a pre-setup API Key perhaps stored in an environment variable is a no go?

(As opposed to passing it as a token in a url, since EXB does not yet honor a lot of the url parameters that WebAppBuilder might have?)