Avamar: Creating OAuth2 Client from Swagger UI Fails with Unauthorized Error
Summary: Failed to create the OAuth2 user from Swagger UI in Avamar version 19.7, resulting in an unauthorized error.
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
An issue is experienced creating an OAuth2 user from the Swagger UI.
- An
OAuth2 usercannot be created from the Swagger UI as it results in a failed attempt. - A solution to create an
OAuth2 userfrom the Swagger UI without using the command line is required.
curl -k \ -H "Content-Type:application/json" \ -H 'authorization:Basic cm9vdDpOQUxBLVN1cHAwcnQtMDAw' \ -X POST -d '{"accessTokenValiditySeconds": 1800, "authorizedGrantTypes": ["password"], "autoApproveScopes": ["all" ], "clientId": "felixtest", "clientName": "felixtest", "clientSecret": "xxxxxxxx", "redirectUris": [ "https://my-app-server/callback" ], "refreshTokenValiditySeconds": 43200, "scopes": ["read", "write"]}' \ https://10.n.n.119/api/v1/oauth2/clients
The issue can be reproduced using the following steps:
-
Log in to the Swagger UI using
MCUser. -
Use other functions in the Swagger UI, such as listing activities and clients, with a token.
-
Attempt to create a new
OAuth2 clientusing the Swagger UI. -
Observe that the creation of the
OAuth2 clientfails.
Cause
The root cause of the issue is related to the authentication process when creating an
OAuth2 client using Swagger UI.
-
The issue is not related to any environmental changes or system configurations, but rather a misunderstanding of the authentication process.
-
The root cause of the issue is the incorrect assumption that the
OAuth2 clientcan be created using Swagger UI without proper authentication.
Resolution
The resolution to the issue of failed OAuth2 user creation from Swagger UI requires understanding the correct authentication process and the minimum privileges required to create an OAuth2 client.
- First, ensure that the user attempting to create the
OAuth2 clienthas the correct authentication credentials. The admin guide mentions using admin credentials, specifically theMCUseraccount. - When creating an
OAuth2client from Swagger UI, the post call should be executed without authorizing the Swagger UI in the beginning. During execution of the post call, provide credentials and sign in. - To execute other API calls under the
oauth2-clientcontroller, first authorize the Swagger UI with proper credentials and then trigger the calls. - Test with different roles to confirm that only the admin role can create an
OAuth2 client. This is mentioned in the admin guide. - Use the following steps to create an
OAuth2 clientfrom Swagger UI:- Open Swagger UI and go to the
oauth2-clientcontroller. - Click the "Create
OAuth2 Client" button. - Enter the required details, such as client name, client ID, client secret, and redirect URLs.
- Click the "Execute" button to create the
OAuth2 client.
- Open Swagger UI and go to the
- Verify that the
OAuth2 clienthas been created successfully by checking the Swagger UI response. - If the issue persists, check the rest API logs for any errors or issues.
- Consult the Avamar documentation and the admin guide for more information about creating
OAuth2 clientsand the minimum privileges required.
Caution: If unsure about any of the steps or there are concerns, Contact Dell Support for assistance.
Additional Information
For more information, see Jira AVAMARESC-2460.
Affected Products
Avamar ServerArticle Properties
Article Number: 000240375
Article Type: Solution
Last Modified: 27 Apr 2026
Version: 2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.