-
Notifications
You must be signed in to change notification settings - Fork 29
docs: add sso okta + jumpcloud configurations #340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
| Ensure that the correct users and groups have access to the Okta SAML app. Only assigned users will be able to authenticate into LocalStack via SSO. | ||
|
|
||
|
|
||
| ## Attribute mapping |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we still need this section, @lukqw? feels duplicate considering the new content?
|
Poke @lukqw 😸 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question: this seems duplicated from the screenshot above?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question: Would it make sense to split this based on provider?
We already have a separate page for Azure AD.
|
poke @quetzalliwrites 😄 |
|
@HarshCasper tyvm! |
|
@HarshCasper we have updated screenshots now, @lukqw redid them. Let us know if this looks good now :) |
quetzalliwrites
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @HarshCasper, I see the build is failing, why is this npm module giving a 404? 🤔
No wrangler.toml file found. Continuing.
--
10:54:20.821 | Detected the following tools from environment: npm@10.9.2, nodejs@22.16.0
10:54:20.822 | Installing project dependencies: npm clean-install --progress=false
10:54:30.155 | npm error code E404
10:54:30.155 | npm error 404 Not Found - GET https://registry.npmjs.org/starlight-toc-overview-customizer/-/starlight-toc-overview-customizer-0.1.0.tgz - Not found
10:54:30.155 | npm error 404
10:54:30.156 | npm error 404 'starlight-toc-overview-customizer@https://registry.npmjs.org/starlight-toc-overview-customizer/-/starlight-toc-overview-customizer-0.1.0.tgz' is not in this registry.
10:54:30.156 | npm error 404
10:54:30.156 | npm error 404 Note that you can also install from a
10:54:30.156 | npm error 404 tarball, folder, http url, or git url.
10:54:30.157 | npm error A complete log of this run can be found in: /opt/buildhome/.npm/_logs/2026-02-10T09_54_21_173Z-debug-0.log
10:54:30.189 | Error: Exit with error code: 1
10:54:30.189 | at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
10:54:30.189 | at Object.onceWrapper (node:events:652:26)
10:54:30.189 | at ChildProcess.emit (node:events:537:28)
10:54:30.189 | at ChildProcess._handle.onexit (node:internal/child_process:291:12)
10:54:30.199 | Failed: build command exited with code: 1
10:54:31.356 | Failed: error occurred while running build command
This was recently fixed in |
No description provided.