Skip to main content
Announcements
Qlik Introduces a New Era of Visualization! READ ALL ABOUT IT

Qlik Cloud: The authentication token associated with auto Provisioning is about to expire Or has expired

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Rakesh_HB
Support
Support

Qlik Cloud: The authentication token associated with auto Provisioning is about to expire Or has expired

Last Update:

May 15, 2024 7:51:37 AM

Updated By:

Sonja_Bauernfeind

Created date:

May 15, 2024 6:56:23 AM

The Qlik Cloud Management Console displays a warning or error message, indicating that although you have stopped using SCIM, there is still a potential issue or misconfiguration that needs attention.

The authentication token associated with auto Provisioning is about to expire

About to Expire.png

Or

The authentication token associated with auto Provisioning has expired

Expired.png

 

Resolution

The token must be deleted that was created for SCIM Auto-provisioning with Azure.

  1. Generate a developer API key in your SaaS platform from the profile settings, ensuring that API keys are enabled for the tenant.
  2. Using a tool like Postman or any other HTTP client, execute the following curl command to retrieve the API key ID associated with SCIM provisioning: 
    curl "https://<tenanthostname>/api/v1/api-keys?subType=externalClient" \ -H "Authorization: Bearer <dev-api-key>"
  3. Ensure to replace <tenanthostname> with your actual tenant hostname and <dev-api-key> with your generated developer API key. Execute the command in Postman or a similar tool, and make sure to include the API key in the header for authorization.

  4. Once you have obtained the key ID from the output, copy it for later use in the deletion process.

  5. To delete the API key associated with SCIM provisioning, execute the following curl command:

    curl "https://<tenanthostname>/api/v1/api-keys/<keyID>" \ -X DELETE \ -H "Authorization: Bearer <dev-api-key>"
  6. Again, replace <tenanthostname> with your actual tenant hostname, <keyID> with the key ID you obtained in step 2, and <dev-api-key> with your developer API key. Execute this command in Postman or a similar tool, and ensure that the API key is included in the header for authorization.

By following these steps, you can successfully delete the token created for SCIM Auto-provisioning with Azure.

 

The information in this article is provided as-is and is to be used at your own discretion. Depending on the tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

 

Cause

The token was not deleted when the SCIM Auto-Provisioning was disabled or completely removed.

 

Environment

Qlik Cloud 

 

Labels (1)
Comments
AlexOmetis
Partner Ambassador
Partner Ambassador

Can you clarify when this applies? Is it just when you've stopped using SCIM but there's an "orphaned" API key that triggers the alert? Or is this required any time the key expires before you can then go back and create a new one in the console? 

Rakesh_HB
Support
Support

Hello @AlexOmetis ,

In this scenario, it is when you have stopped using SCIM but there is an "orphaned" API key that triggers the above alert.

Version history
Last update:
2 weeks ago
Updated by: