OAuth 2.0 Troubleshooting
Have you completed all the steps described in the topic, Preparation?
The following is a trouble-shooting guide to errors that may occur and how you might solve them. Troubleshooting should begin by reviewing the list of what you must do before configuring OAuth 2.0. See the topic "Preparation" within OAuth 2.0 Configuration
Error Messages related to Provider Configuration
The URL you provided does not follow the standard form. Check for errors.
(VTScada has not checked whether the location is valid, only that the URL is written in a way that will not access any location.) For reference, the URLs for two common providers are shown here:
https://login.microsoftonline.com/ 236fb237-d18f-42c0-b59a-845ad5e04584 /oauth2/v2.0/authorize
https://accounts.google.com/o/oauth2/v2/auth
A Provider Name must be unique
You have attempted to give a new provider the same name as an existing provider. Choose a new name for the new provider.
Each configured provider must be given a unique name. Names can be anything you like, but we suggest creating one that clearly identifies the provider.
Failed to add OAuth 2.0 Provider
VTScada was unable to complete the process of adding this provider. Check all fields for errors. Ensure that all URLs can be reached from this workstation.
Failed to modify OAuth 2.0 Provider
VTScada was unable to complete the process of changing this provider. This will fail if a grant is still active and using the information that will be modified.
Failed to delete OAuth 2.0 Provider
This will fail if a grant is still active for this provider. VTScada attempts to revoke the grants, but may not be able to do so in all cases.
Each grant must have a defined redirect URI
Uniform Resource Identifier. Select one using the Redirect URI Editor in the OAuth 2.0 Configuration's Settings dialog.
The Redirect URI you are attempting to create already exists.
Provider scope contains spaces
Spaces are not permitted in the provider scope field.
The provider scope you are attempting to create already exists.
Error Messages related to Grant Configuration
Each configured grant must be given a unique name. Names can be anything you like, but we suggest creating one that clearly identifies the grant.
You have attempted to give a new grant the same name as an existing grant under the selected provider. Grant names may be reused so long as each is under a different provider. In the current case, choose a new name for the new grant.
Each grant must have a defined scope. Select one using the Scope Editor in the OAuth 2.0 Configuration's Settings dialog.
VTScada was unable to complete the process of adding this grant. Check all fields for errors.
Failed to modify OAuth 2.0 Grant
VTScada was unable to complete the process of changing this grant. Check all fields for errors. Modifying the grant will also fail if the grant is still active and the modification will affect information sent to external sources.
Failed to delete OAuth 2.0 Grant
An attempt to delete a grant will fail if it is not revoked. This revocation is handled by VTScada but it may not be possible to do automatically in all cases.
Incomplete configuration. You must define the Grant Bearer.
Warning on deleting a provider - associated grants
Grants are linked to providers and will be removed when the provider is removed. Use the OK button in this dialog to confirm that you wish to proceed.
Warning: Grant revocation on provider scope removal
This warning appears when editing scopes for the provider. Any grants using a scope deleted for this provider will be revoked. Use the OK button to continue.
Warning: Grant not revoked on provider scope removal
A grant could not be revoked while attempting to modify the provider scopes. Look for the active grant and attempt to revoke it using the Revoke button.
