-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
User Problem
Using an invalid Client secret doesn't provide any feedback to the user. So customers can:
- Connect SharePoint to Rovo with an invalid Client secret value.
- There is no UI error, and configuration can be completed. Still, the number of connectors remains zero since the connector isn't correctly configured.
Suggested Solutions
Provide some feedback in the UI that an invalid Client secret was used so this can be reviewed and addressed.
Current Workarounds
Checking the network logs on the browser, we observe:
Request URL | https://admin.atlassian.com/gateway/api/admin/private/api/v1/third-party-configuration/sharepoint-domains/<redacted>/<redacted> |
Request Method | POST |
Status Code | 401 Unauthorized |
This could confirm the issue and help focus attention on the authentication part of the configuration.