8000 Login required for local deployment · Issue #126 · nomad-coe/nomad · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Login required for local deployment #126

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

Open
fleimgruber opened this issue Apr 14, 2025 · 2 comments
Open

Login required for local deployment #126

fleimgruber opened this issue Apr 14, 2025 · 2 comments

Comments

@fleimgruber
Copy link

I followed https://nomad-lab.eu/prod/v1/docs/howto/oasis/install.html#basic-installation and tried to upload data at http://localhost/nomad-oasis/gui/user/uploads but see "You have to login to use this functionality.". I expected to be able to use nomad on-prem without needing to interact with https://nomad-lab.eu. Maybe add this to the docs so there is less room for wrong expectations? What is the motivation behind this requirement?

@lauri-codes
Copy link
Contributor

Hi @fleimgruber!

Some of the functionality in NOMAD requires you to login, so that we can attribute the data to a user. By default Oasises are configured to use our central authentication server, since this simplifies things quite considerably from the perspective of the Oasis.

It is possible to connect your own authentication service. This is documented here. This way your Oasis does not need to connect to nomad-lab.eu anymore.

We will update the documentation to highlight this default authentication flow and the alternative of setting up your own authentication 👍

@fleimgruber
Copy link
Author

Hi @lauri-codes!

Thanks for the quick reply, explanation and pointer; we do have a keycloak service running on-prem so good to hear that you support that!

Please close/keep-open according to how you want to track the documentation update - it's solved for me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
0