Skip to content

Commit 5610328

Browse files
authored
[docs] sso maintenance (#12356)
* Update configure_sso.md * Update configure_sso.md
1 parent 6601929 commit 5610328

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

docs/content/en/customize_dojo/user_management/configure_sso.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -315,8 +315,9 @@ In order to use Google Authentication, a Google Authentication Server will need
315315
- **Google OAuth Secret** should be set to your **Client Secret Key**.
316316
- **Whitelisted Domains** can be set to the domain name used by your organization. However, this will allow login from any user with this domain name in their Google email address.
317317
- Alternatively, if you only want to allow specific Google email addresses to log in to DefectDojo, you can enter those in the **Whitelisted E-mail Addresses** section of the form. `(appsecuser1@xyz.com,appsecuser2@xyz.com)`, etc.
318+
- Note that you must add at least one user or domain to the whitelist, or DefectDojo will not allow any users to log in using Google OAuth.
318319

319-
2. Check the **Enable Azure AD OAuth** box. Submit the form, and `Login With Google` will be added as an option to the Login menu.
320+
2. Check the **Enable Google OAuth** box. Submit the form, and `Login With Google` will be added as an option to the Login menu.
320321

321322
### Open-Source
322323

@@ -678,4 +679,4 @@ ecosystem as it has a library of compatible providers with documentation
678679
of implementation. Conveniently, each provider has an identical
679680
procedure of managing the authenticated responses and authorizing access
680681
within a given application. The only difficulty is creating a new
681-
authentication client with a given OAuth2 provider.
682+
authentication client with a given OAuth2 provider.

0 commit comments

Comments
 (0)