Connection Management - Azure Key Vault
We use basic authentication for a connection (to Anaplan, in this instance). Due to this, we have to rotate the password quarterly, which can frequently lead to lapses in connectivity (also, Anaplan allows 5 incorrect sign ins for our integration user and then locks it out). Instead of manually having to update the password/credentials, we have been exploring using Azure Key Vault to rotate the credentials and better manage the process. To our knowledge, there is no Workiva connector to AKV, nor is there a way to write to the 'Connections' metadata in the Chains environment. Can you suggest any alternate routes, updated guidance, etc. for this process?
-
Hi Joe Rufolo,
The Anaplan (Standard) Connector supports Basic username/password and Anaplan OAuth2 Authorization Code authentication. For OAuth 2.0, the Anaplan OAuth client's Refresh Token Behavior must be set to non-rotatable.
For this situation, your Anaplan administrator would be a good first point of contact to confirm the quarterly integration password rotation requirement. OAuth 2.0 could eliminate the dependency on the integration user's Anaplan password, but I recommend confirming with your Anaplan administrator that OAuth 2.0 is appropriate for the process and can be configured with the required non-rotatable refresh token setting.
If OAuth 2.0 is not an option, another possible approach would be to use the Anaplan REST API directly via the HTTP Request Connector. This may provide more control over authentication and credential management, although it would require implementing the API calls in your Chains.
0Zaloguj się, aby dodać komentarz.
Komentarze
Komentarze: 1