Download the PHP package magedevgroup/module-customer-sso-okta without Composer

On this page you can find all versions of the php package magedevgroup/module-customer-sso-okta. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package module-customer-sso-okta

MageDevGroup_CustomerSsoOkta

Okta login for the Magento 2 storefront.

License Magento PHP Version

Thin Okta provider plugin for the customer-sso storefront SSO capability. It ships an Okta ProviderPreset (discovery URL, scopes, groups claim, branding) plus Okta org-domain config, and registers it into customer-sso's PresetRegistry — all OIDC protocol and storefront logic live upstream. Installing it pulls customer-sso and, transitively, sso-core.

Installation

Create the Okta OIDC app

In the Okta Admin Console → Applications → Create App Integration:

  1. Sign-in method OIDC - OpenID Connect, application type Web Application.
  2. Sign-in redirect URI — the customer-sso callback: https://<store-host>/customersso/sso/callback. It must match the storefront URL used at runtime exactly.
  3. Save, then copy the Client ID and Client secret.
  4. Groups claim — for IdP-group → customer-group mapping, add a groups claim to the ID token: Sign On → OpenID Connect ID Token → Groups claim, filter e.g. Matches regex .*. Without this Okta emits no groups and group mapping falls back to the default customer group.

Configuration

Admin → Stores → Configuration → MageDevGroup → Customer SSO (store-scoped — tune per store view).

General (magedevgroup_customer_sso/general/*):

Field Value
Enable Customer SSO Yes
Identity Provider Okta
Client ID from the Okta app
Client Secret from the Okta app

Okta (magedevgroup_customer_sso/okta/*, shown when Okta is selected):

Field Value
Org Domain your org domain, e.g. dev-123.okta.com (scheme optional, https assumed)
Custom Authorization Server optional server id (e.g. default); empty = org server

The discovery URL is derived from these: https://<domain>/.well-known/openid-configuration, or https://<domain>/oauth2/<auth-server>/.well-known/openid-configuration with a custom authorization server.

Account linking by email, keep-password-login, and group → customer-group mapping are configured in customer-sso; see that module's README.

Design decisions

Okta preset: duplicated, not shared. admin-sso-okta ships the first Okta preset; this is the second consumer. The preset is duplicated here rather than extracted into a shared sso-okta module because:

Extraction stays open if the copies grow or drift (rule of three) — not yet earned at the 2nd consumer.

Requirements

Part of the MageDevGroup identity suite

Repo Role
sso-core Shared OIDC engine (installed automatically)
admin-sso · admin-sso-<idp> Admin-panel SSO login
customer-sso · customer-sso-<idp> Storefront SSO login
admin-scim · admin-scim-<idp> Admin-user provisioning (SCIM 2.0)

License

https://magedevgroup.com.

All versions of module-customer-sso-okta with dependencies

PHP Build Version
Package Version
Requires php Version ~8.3.0||~8.4.0||~8.5.0
magento/framework Version >=103.0
magedevgroup/module-customer-sso Version *
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package magedevgroup/module-customer-sso-okta contains the following files

Loading the files please wait ...