Skip to content
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

Default realm is always returned with HTTP 401 #5284

Closed
sberyozkin opened this issue Nov 7, 2019 · 1 comment · Fixed by #8006
Closed

Default realm is always returned with HTTP 401 #5284

sberyozkin opened this issue Nov 7, 2019 · 1 comment · Fixed by #8006
Labels
area/security kind/bug Something isn't working
Milestone

Comments

@sberyozkin
Copy link
Member

Describe the bug
Andrey has reported that a default Quarkus realm is returned with 401 even when a property such as quarkus.security.users.file.realm-name=MyRealm is set.

Expected behavior
WebAuthenticate needs to have a custom realm name set.

@belyaev-andrey
Copy link

It looks like this is it and you're aware of this issue.

io.quarkus.vertx.http.runtime.security.HttpAuthenticator
lines 43 - 48

            if (!usernamePassword.isUnsatisfied()) {
                //TODO: config
                mechanism = new BasicAuthenticationMechanism("Quarkus");
            } else {
                mechanism = new NoAuthenticationMechanism();
            }

stuartwdouglas added a commit to stuartwdouglas/quarkus that referenced this issue Mar 20, 2020
- Use synthetic beans to configure form and basic auth
- Allow multiple authentication mechanisms
- Better default behaviour based on what is configured

Fixes quarkusio#7768
Fixes quarkusio#5284
stuartwdouglas added a commit to stuartwdouglas/quarkus that referenced this issue Mar 20, 2020
- Use synthetic beans to configure form and basic auth
- Allow multiple authentication mechanisms
- Better default behaviour based on what is configured

Fixes quarkusio#7768
Fixes quarkusio#5284
stuartwdouglas added a commit to stuartwdouglas/quarkus that referenced this issue Mar 26, 2020
- Use synthetic beans to configure form and basic auth
- Allow multiple authentication mechanisms
- Better default behaviour based on what is configured

Fixes quarkusio#7768
Fixes quarkusio#5284
gsmet pushed a commit to gsmet/quarkus that referenced this issue Mar 26, 2020
- Use synthetic beans to configure form and basic auth
- Allow multiple authentication mechanisms
- Better default behaviour based on what is configured

Fixes quarkusio#7768
Fixes quarkusio#5284
gsmet pushed a commit to gsmet/quarkus that referenced this issue Mar 26, 2020
- Use synthetic beans to configure form and basic auth
- Allow multiple authentication mechanisms
- Better default behaviour based on what is configured

Fixes quarkusio#7768
Fixes quarkusio#5284
@gsmet gsmet added this to the 1.3.1.Final milestone Mar 26, 2020
viniciusfcf pushed a commit to viniciusfcf/quarkus-fork that referenced this issue Sep 7, 2020
- Use synthetic beans to configure form and basic auth
- Allow multiple authentication mechanisms
- Better default behaviour based on what is configured

Fixes quarkusio#7768
Fixes quarkusio#5284
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/security kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants