Search Results :
×AWS Cognito Single Sign-On (SSO) for WordPress uses OAuth Authorization flow to provide users secure access to WordPress site. With our WordPress OAuth Single Sign-On (SSO) plugin, AWS Cognito acts as the OpenID Connect and OAuth provider, ensuring secure login for WordPress websites.
The integration of WordPress with AWS Cognito simplifies and secures the login process using AWS Cognito OAuth. This solution allows employees to access their WordPress sites with Single Sign-On (SSO) using their AWS Cognito credentials, completely removing the need to store, remember, and reset multiple passwords.
In addition to offering AWS Cognito SSO functionality, the WordPress SSO plugin extends its support to a various IDPs, including Azure AD, Office 365, and specialized providers, offering robust SSO capabilities like multi-tenant login, role mapping, and user profile attribute mapping. For a detailed overview of the features, check out the WordPress OAuth Single Sign-On (SSO) plugin. You can follow the below steps to setup AWS Cognito Single Sign-On (SSO) with WordPress
WordPress Cognito Integration uses the Cognito SDK and allows users to fill Registration and Password Reset forms or log into the WordPress website directly.
In case you have enabled AWS Federation and would like to allow users to authenticate only via certain identity providers, then please select the desired OR targeted provider from the dropdown menu.
In conclusion, by successfully configuring AWS Cognito as OAuth Provider, you have enabled seamless AWS Cognito Single Sign-On (SSO) and authorization for your end users into WordPress.
Scopes | openid |
Authorize Endpoint: | https://<cognito-app-domain>/oauth2/authorize |
Access Token Endpoint: | https://<cognito-app-domain>/oauth2/token |
Get User Info Endpoint: | https://<cognito-app-domain>/oauth2/userInfo |
Custom redirect URL after logout:[optional] | https://<cognito-app-domain>/logout?client_id=<Client-ID>&logout_uri=<Sign out URL configured in Cognito Portal> |
In conclusion, by successfully configuring WordPress as OAuth Client, you have enabled seamless AWS Cognito Single Sign-On (SSO) and authorization for your end users into WordPress.
Please refer the below table for configuring the scope & endpoints for Amazon Cognito in the plugin.
Client ID : | Click Here |
Client Secret : | Click Here |
Scope: | openid |
Authorize Endpoint: | https://<cognito-app-domain>/oauth2/authorize |
Access Token Endpoint: | https://<cognito-app-domain>/oauth2/token |
Get User Info Endpoint: | https://<cognito-app-domain>/oauth2/userInfo |
Custom redirect URL after logout:[optional] | https://<cognito-app-domain>/logout?client_id=<Client-ID>&logout_uri=<Sign out URL configured in Cognito Portal> |
You have successfully configured WordPress as OAuth Client for achieving user authentication with AWS Cognito Single Sign-On (SSO) login into your WordPress Site.
Sign in settings for WordPress 5.7 and before
Sign in settings for WordPress 5.8
Sign in settings for WordPress 5.9
In conclusion, after successfully configuring AWS Cognito as an OAuth Provider and WordPress as an OAuth Client, you've achieved a smooth and secure authentication process for your users. Through AWS Cognito Single Sign-On (SSO), you can ensure a robust user experience within the WordPress environment. This allows users the ease of accessing multiple applications with a single set of login credentials. Through the integration of AWS Cognito OAuth as the primary authentication solution, users can securely log into their WordPress accounts with their existing AWS Cognito credentials.
To fix this issue, please configure the correct Authorization endpoint in the plugin. You can confirm the correct format of the endpoint from here.
Please make sure if you have entered correct Scopes in the plugin. You verify steps from this setup guide.
To fix this issue, please configure the correct Redirect url in the Cognito Developer application from the plugin . You can refer to the steps in the setup guide here.
To fix this issue, please configure the correct Client Secret in the plugin. You can refer to this steps to configure correct Client Secret from the setup guide.
If your error is not listed here, click here to see others.
Go to your user pool in Cognito. Under General Settings, go to Policies. Select the option Only allow administrators to create users and Save Changes. Read more
This error has probably occurred because you might not have enabled the following checkboxes ‘username password auth for admin APIs for authentication’ and ‘username password-based authentication’ while configuring the App client in Cognito User Pool. Read more
Mail us on oauthsupport@xecurify.com for quick guidance(via email/meeting) on your requirement and our team will help you to select the best suitable solution/plan as per your requirement.
Need Help? We are right here!
Thanks for your inquiry.
If you dont hear from us within 24 hours, please feel free to send a follow up email to info@xecurify.com
This privacy statement applies to miniorange websites describing how we handle the personal information. When you visit any website, it may store or retrieve the information on your browser, mostly in the form of the cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not directly identify you, but it can give you a more personalized web experience. Click on the category headings to check how we handle the cookies. For the privacy statement of our solutions you can refer to the privacy policy.
Necessary cookies help make a website fully usable by enabling the basic functions like site navigation, logging in, filling forms, etc. The cookies used for the functionality do not store any personal identifiable information. However, some parts of the website will not work properly without the cookies.
These cookies only collect aggregated information about the traffic of the website including - visitors, sources, page clicks and views, etc. This allows us to know more about our most and least popular pages along with users' interaction on the actionable elements and hence letting us improve the performance of our website as well as our services.