This Shopware 6 plugin allows to add "Login with" functionality into the Shopware administration login page and password confirmation dialogs.
- login to Shopware 6 administration using an external identity provider (IDP)
- various providers already preconfigured - Microsoft, Google, Okta, Keycloak, ...
- support for third-party IDPs supporting OpenID Connect
- easy setup using the provider's metadata document (
.well-known/openid-configuration)
- easy setup using the provider's metadata document (
- support for third-party IDPs supporting SAML2
- easy setup using the provider's metadata xml
- promote users automatically to administrators
The login to the Shopware administration is a critical part. Security vulnerabilities in this part allow attackers access to the whole shop.
Therefore, we check our plugin critically for potential risks before merging pull requests.
In addition, our OpenId Connect implementation also checks the signature of JWT tokens, whenever possible. When using a pre-configured OpenID Connect provider or when providing a OIDC metadata document, the JWKS keys are automatically fetched from the IDP.
We support a variety of identity providers out of the box. If your identity provider is not listed below but offers OpenID Connect support, you can configure it manually using the OpenID Connect provider. In any other case feel free to create a pull request.
| Provider | supports language sync | supports timezone sync | more info |
|---|---|---|---|
Atlassian Jira |
❌ | ✅ | Read more here. |
cidaas |
❌ | ❌ | Read more here. |
Google Cloud |
✅ | ❌ | Read more here. |
| JumpCloud | depends on configuration | depends on configuration | Read more here. |
Keycloack |
✅ | depends on configuration | Read more here. |
Microsoft Azure |
❌ | ❌ | Read more here. |
Okta |
✅ | ✅ | Read more here. |
OneLogin |
✅ | ❌ | Read more here. |
OpenID Connect |
depends on configuration | depends on configuration | Try any OpenID Connect provider, that we did not explicitly prepare an optimized configuration for. |
SAML2 |
depends on configuration | depends on configuration | Try any SAML2 provider, that we did not explicitly prepare an optimized configuration for. |
In case you want to use a SAML2 provider, your IdP must meet the following requirements:
- include AuthnRequest in the SAML response
- sign the returned assertions
- support HTTP-POST binding for the Assertion Consumer Service (ACS)
- return the user's email address as attribute (all other attributes are optional)
View the CHANGELOG file attached to this project.
Thank you for considering contributing to this package! Be sure to sign the CLA after creating the pull request.
Copyright 2020 HEPTACOM GmbH
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this project except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 or see the local copy.
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
All logos, available in this project are protected under copyright. Most of them also are registered trademarks. Therefore, the usage is only permitted when corresponding trademark/branding guidelines are fulfilled. You can find an archived link to these guidelines below.
- https://developers.google.com/identity/branding-guidelines
- https://about.google/brand-resource-center/brand-elements/
- https://about.google/brand-resource-center/rules/
- https://about.google/brand-resource-center/brand-terms/
The One Identity logo is a registered trademark of One Identity, Inc.