User unable to get an OAuth 2.0 access tokenIssue After creating an application registry record, a user is not able to get the OAuth 2.0 access token. When attempting to get the access token, this error may be returned: No_Oauth_Token: server_error access_deniedReleaseAll releases.CauseThe user may have the snc_read_only role and therefore isn't able to write to the oauth_credential table during token creation.ResolutionYou can keep the snc_read_only role for the user but allow an exception where they can write to the oauth_credential table. Please verify this on a subprod instance first:1. Create a new system property.Name: glide.security.snc_read_only_role.tables.exempt_createType: stringValue: sys_user_session, sysevent, syslog, syslog_transaction, sys_user_preference, sys_ui_list, sys_ui_list_element, sys_db_cache, user_multifactor_auth, oauth_credential You're retaining the default (back-end) value as documented here: Read-only roleand adding only the necessary oauth_credential table. 2. Click Submit. Verify that this user is able to get an OAuth 2.0 access token through a third-party tool such as Postman.