I am experiencing caching issues when updating AdminUI
This is typically due to the index.html file being cached in the browser. Whilst AdminUI has aggressive default caching in the index.html file these settings could be overriden by certain setups. If this is the case or you need to change the defaults we recommend updating your webserver following the guidelines from the mozilla documentation.
When updating/deleting a user/client/resource AdminUI is unable to perform the action and a CORS error is in the console.
If you can sign in but not update users/clients/resources then you may have something blocking PUT/DELETE requests on your environment
I have installed AdminUI, but it is in a foreign language.
The website uses your browser culture to check what language to display. You can either change your browser language or change the route to use your preferred culture of choice: e.g: http://YourAdminUI-UI/en-GB.
When running migrations I get a Create Unique Index error
If you see and error similar to the following:
CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.ClientScopes' and the index name 'IX_ClientScopes_ClientId_Scope'. The duplicate key value is (1, admin_api).
This usually occurs when trying to upgrade to an AdminUI versions from before we introduced a unique index on the ClientScopes and ApiScopes tables.
The fix is to rename duplicate ApiScopes and remove duplicate entries from the ClientScopes table.
I’m getting a HTTP Error 500.19 - Internal Service Error when starting AdminUI.
Please download and run the dotnet core hosting bundle.
For those on AdminUI 6.x.x and above please use the following link:
For those on AdminUI 3.x.x to 5.x.x and above please use the following link:
If you are running AdminUI 2.6 and below please use the following link:
If this fails to work and your configuration looks correct please send us a copy of your AdminUI logs to [email protected] and we will be able to help as soon as possible.
When starting AdminUI I get the following message - “An unhandled exception occurred while processing the request. AggregateException: One or more errors occurred. (One or more errors occurred. (Failed to start 'npm')”
This is due to your ASPNETCORE_ENVIRONMENT being set to “Development”. to change this set the ASPNETCORE_ENVIRONMENT variable to “Production” Either in your appsettings.json or your web.config
When running AdminUI on a path, the path is stripped from UI requests
Please use the X-Forwarded-Prefix header to allow AdminUI to attach your path to the PathBase of the request.
For example in nginx this would look like:
proxy_set_header X-Forwarded-Prefix /admin;
My license key is invalid, what do I do?
Please ensure that you have only copy pasted the Base64 string. Example:
Ensure there are no additional characters before or after the license key.
If your license key has expired or is setup against an AuthorityUrl you did not expect. Please contact [email protected]
What is the difference between a blocked user and a deleted user? How are they treated in AdminUI?
The 'IsDeleted' attribute is typically employed for a soft delete, preserving user information for auditing purposes. On the other hand, 'IsBlocked' is typically utilized in scenarios where a password has been compromised, preventing login until the password is reset.
In the default User Store of AdminUI, users are not deleted from the database but rather have 'IsDeleted' set to true for auditing. Consequently, these users disapear from the user list but users could still log in if your IdentityServer login conditions are not configured accordingly.
The primary impact on AdminUI is that users marked with either of these attributes will not be visible in the user list.
To prevent confusion, consider one of the following options:
- Integrate the 'IsDeleted' field into your authentication logic, disallowing login for any user marked with this attribute.
- Develop your custom user store and perform a hard delete on the user when the delete button is pressed (not recommended). Keep in mind that this approach will result in the loss of audit entry information related to that user. The documentation for adding a custom user store can be found here: Custom Identity Overview.