Join Free or Sign in
Share:
My Cart 0
€0.00

Customer Single Sign-On with OKTA

SKU
Customer Single Sign-On with OKTA
€199.00

Allow your Magento 2 Customer to login directly with OKTA without having to go through the account creation process.

When your customergoes to the login page, they will see the option to login with Single Sign-On. They simply click the button and after logging in he will be redirected to the shop and logged in. If the user does not exist in the shop, an account will be automatically created.

Our Single Sign-On solutions have been implemented in hundereds of webshops world wide, including Nokia, Canon, Castrol, Pearson, Dentons and numerous more. We have learned from every of these implementations and this is where you directly profit from

You can have your customers connect to your Single Sign-On environment in no time and increase the revenue of your webshop by removing barriers.


Compatibility Details

Magento 2.4.X

Extension v1.0
Installation Instructions
composer require gogento/sso-okta-frontend "^240.1"

Single Sign-On with OKTA for your Magento 2 Webshop

Allow your Magento 2 Customer to login directly with OKTA without having to go through the account creation process.

When your customergoes to the login page, they will see the option to login with Single Sign-On. They simply click the button and after logging in he will be redirected to the shop and logged in. If the user does not exist in the shop, an account will be automatically created.

Our Single Sign-On solutions have been implemented in hundereds of webshops world wide, including Nokia, Canon, Castrol, Pearson, Dentons and numerous more. We have learned from every of these implementations and this is where you directly profit from

You can have your customers connect to your Single Sign-On environment in no time and increase the revenue of your webshop by removing barriers.


General Single Sign-On Configuration

Send customer registration welcome email on first login

When the account is created in the webshop, after a first login, you have the option to automatically send the welcome email which a customer would get on a normal registration. Generally you should set this to yes if you are running a business to consumer webshop.

CMS Page for failed login

When the login fails because the customer registration cannot be completed, we set a landing page that the customer will be directed to. Usually if SSO fails, it means incomplete data at the identity provider, so therefor instructions to request support can be given on the landing page.

Website visible for guests

In some occasions you want your webshop only to be visible to users who are logged in. If you set this to yes, the webshop will immediately redirect to the identity provider when the customer lands on any landingpage which is not set public. If you set this setting to "no", a whitelist option appears.




OKTA Single Sign-On Configuration

First, create your SSO application in your OKTA account.

Entity ID

After creating the SSO application, fill in the Entity ID which you filled in into the OKTA SSO settings

Metadata Endpoint

In your OKTA account copy the Identity Provider Metadata URL which you can find on the SSO settings page.

Single Sign-On Binding And Single Logout Binding

Keep this setting at the default, you do not need to change it. This is changeable because some users use specific binding settings. By defaults its best to use HTTP-POST for your Single Sign-On and HTTP-Redirect for your Single Logout.

Solution Enabled

Go to the right scope where you want to enable Single Sign-On and set this setting to Yes, to enable it for that specific website or store.



Done!



Installation and Upgrade Details

We do not provide direct download links of our extensions as they are not needed and bad practise. Installing and maintaining the latest updates of your extensions using composer is the best and safest solution. If you do need a manual download, feel free to contact us for aid.

Installing an extension is the same process as upgrading an extension. You can run the exact same composer require command as you do with the installation with the new version set, to upgrade the extension


Step 1 - Setup composer authentication

To install our extensions you need to first setup the composer repository for your account.
You don't need to do this after every purchase, just after the very first purchase you make in our webshop. Your composer URL can be found in your account details and can be setup with composer by executing this command on your server in your Magento 2 root:

composer config repositories.gogento composer https://gogento.com/composer/customer/[your-composer-secret]

These instructions can also be found in your account details


Step 2 - Install the right version

Now find the closest version matching your Magento 2 installation and run the composer require command below.


Magento 2.4.X

Extension v1.0
composer require gogento/sso-okta-frontend "^240.1"

Step 3 - Post Installation

After the extension installation you can proceed with the default deployment commands which are run after adding a new extension.

1. Upgrading the database schema

bin/magento setup:upgrade
2. Verify your deployment mode
bin/magento deploy:mode:show
3. Run if the above command returns "production"
bin/magento setup:di:compile
bin/magento setup:static-content:deploy [your locales]
4. Wrap up the deployment
bin/magento index:reindex
bin/magento cache:clean

19-10-2020 11:46:32

v1.0 for Magento 2.4.0

Added OKTA frontend extension
Recommended Installation Instructions
composer require gogento/sso-okta-frontend "^240.1"
Fixed Version Installation Instructions
composer require gogento/sso-okta-frontend "~240.1.0"

Single Sign-On with OKTA for your Magento 2 Webshop

Allow your Magento 2 Customer to login directly with OKTA without having to go through the account creation process.

When your customergoes to the login page, they will see the option to login with Single Sign-On. They simply click the button and after logging in he will be redirected to the shop and logged in. If the user does not exist in the shop, an account will be automatically created.

Our Single Sign-On solutions have been implemented in hundereds of webshops world wide, including Nokia, Canon, Castrol, Pearson, Dentons and numerous more. We have learned from every of these implementations and this is where you directly profit from

You can have your customers connect to your Single Sign-On environment in no time and increase the revenue of your webshop by removing barriers.


General Single Sign-On Configuration

Send customer registration welcome email on first login

When the account is created in the webshop, after a first login, you have the option to automatically send the welcome email which a customer would get on a normal registration. Generally you should set this to yes if you are running a business to consumer webshop.

CMS Page for failed login

When the login fails because the customer registration cannot be completed, we set a landing page that the customer will be directed to. Usually if SSO fails, it means incomplete data at the identity provider, so therefor instructions to request support can be given on the landing page.

Website visible for guests

In some occasions you want your webshop only to be visible to users who are logged in. If you set this to yes, the webshop will immediately redirect to the identity provider when the customer lands on any landingpage which is not set public. If you set this setting to "no", a whitelist option appears.



Azure Single Sign-On Configuration

First, create your SSO application in your OKTA account.

Entity ID

After creating the SSO application, fill in the Entity ID which you filled in into the OKTA SSO settings

Metadata Endpoint

In your OKTA account copy the Identity Provider Metadata URL which you can find on the SSO settings page.

Single Sign-On Binding And Single Logout Binding

Keep this setting at the default, you do not need to change it. This is changeable because some users use specific binding settings. By defaults its best to use HTTP-POST for your Single Sign-On and HTTP-Redirect for your Single Logout.

Solution Enabled

Go to the right scope where you want to enable Single Sign-On and set this setting to Yes, to enable it for that specific website or store.


Done!