AWS cognito documentation change
Summary
Fixed typo from 'preiodically' to 'periodically' in description of OIDC relying party library behavior
Security assessment
This is a minor typographical correction with no security implications. The content remains the same - recommending automatic discovery of OIDC endpoints to avoid manual configuration errors.
Diff
diff --git a/cognito/latest/developerguide/authentication-flows-selection-managedlogin.md b/cognito/latest/developerguide/authentication-flows-selection-managedlogin.md index d8893e8b6..b06ec9e2c 100644 --- a//cognito/latest/developerguide/authentication-flows-selection-managedlogin.md +++ b//cognito/latest/developerguide/authentication-flows-selection-managedlogin.md @@ -13 +13 @@ The Amazon Cognito user pools console can get you started with setting up manage -Typically, OIDC relying party libraries preiodically check the `.well-known/openid-configuration` endpoint of your user pool to determine issuer URLs like the token endpoint and authorization endpoint. As a best practice, implement this automatic-discovery behavior where you have to option to. Manual configuration of issuer endpoints introduces potential for error. For example, you might change your user pool domain. The path to `openid-configuration` isn't linked to your user pool domain, so applications that autodiscover service endpoints will automatically pick up your domain change. +Typically, OIDC relying party libraries periodically check the `.well-known/openid-configuration` endpoint of your user pool to determine issuer URLs like the token endpoint and authorization endpoint. As a best practice, implement this automatic-discovery behavior where you have to option to. Manual configuration of issuer endpoints introduces potential for error. For example, you might change your user pool domain. The path to `openid-configuration` isn't linked to your user pool domain, so applications that autodiscover service endpoints will automatically pick up your domain change.