![]() Text on the Administrator assignment by admin page was misaligned. When the display language was set to Japanese, the Okta Sign-on Policy page displayed a translation error instead of the Everyone group name. In some orgs, on-premises imports performed using the Okta Provisioning Agent ignored safeguard thresholds.ĭeveloper and free-trial orgs redirected users to the configured redirect URI when errors occurred. ![]() When many apps were added to routing rules through the API, system performance was degraded. The Add Resource dialog box sometimes displayed duplicate group names. Some AD-sourced users received prompts to reset their password even when the AD password policy restricted password changes. When an Okta group name contained $, the push group feature either removed $ or caused the sAMAccountName to fail validation when populating the Active Directory group. ![]() Some text strings on the Okta Sign-on Policy page weren't translated.Ī user with a custom admin role couldn't create federated users due to misplaced permissions. Sometimes users encountered an error when the Self-Service Registration flow made a request to the /tokens endpoint.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |