-
Notifications
You must be signed in to change notification settings - Fork 36
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
Quack user session appears to work BUT will not allow login #239
Comments
|
Attaching to mongod, quack_quack_1 |
whoru.auth.provider=com.testquack.api.security.DbAuthProvider #Hazelcast #Storage #Tracker quack.multi.organization.mode=false #Properties in case CognitoAuthProvider is being used quack.organizations.enabled=false google.analytics.enabled=false |
version: '2' mongod: |
FYI - The same results occur if I use localhost, 127.0.0.1, or the actual local ip address. |
Alternatively you can set up ports like
You'll be able to access quack via http://10.0.2.15 and auth.domain can stay as in your example - auth.domain=10.0.2.15
Lets try the following - replace Try to restart the app and run again. If this will help - you can try returning back Hazelcast provider and point it to itself However, if you are running only a single instance if quack service, you don't need hazelcast. Inmem provider will do just fine. |
I can now create users, projects, and tests when logged in to localhost BUT
not if I use an actual ip address. Can I chat you sometime? Maybe this
afternoon or tomorrow
morning?It would speed up this process.
Bob
…On Tue, Feb 21, 2023 at 5:36 AM Azee ***@***.***> wrote:
1. Make sure that auth.domain=10.0.2.15 matches what you are entering
in the browser. E.g., if you are accessing quack UI using port 8080, like
http://10.0.2.15:8080, then auth domain should reflect that
auth.domain=10.0.2.15:8080
Alternatively you can set up ports like
ports:
- "80:8080"
You'll be able to access quack via http://10.0.2.15 and auth.domain can
stay as in your example - auth.domain=10.0.2.15
1. If that won't help. Might be related to Hazelcast setup.
Lets try the following - replace
whoru.session.provider=ru.greatbit.whoru.auth.providers.HazelcastSessionProvider
with
whoru.session.provider=ru.greatbit.whoru.auth.providers.InmemSessionProvider
Try to restart the app and run again.
If this will help - you can try returning back Hazelcast provider and
point it to itself
hazelcast.members=127.0.0.1
hazelcast.interface=127.0.0.1
However, if you are running only a single instance if quack service, you
don't need hazelcast. Inmem provider will do just fine.
—
Reply to this email directly, view it on GitHub
<#239 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZWTTVWCBARX3SAGHTUQ2H3WYSLEJANCNFSM6AAAAAAVCIF5RY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Working now for localhost. See issue #240. Now I want to get it to work
when i point my browser to the ip address and I want
anything I create (db, user, test case) to be persisted.
Bob
…On Tue, Feb 21, 2023 at 12:39 PM Bob Beck ***@***.***> wrote:
I can now create users, projects, and tests when logged in to localhost BUT
not if I use an actual ip address. Can I chat you sometime? Maybe this
afternoon or tomorrow
morning?It would speed up this process.
Bob
On Tue, Feb 21, 2023 at 5:36 AM Azee ***@***.***> wrote:
>
> 1. Make sure that auth.domain=10.0.2.15 matches what you are entering
> in the browser. E.g., if you are accessing quack UI using port 8080, like
> http://10.0.2.15:8080, then auth domain should reflect that
> auth.domain=10.0.2.15:8080
>
> Alternatively you can set up ports like
> ports:
>
> - "80:8080"
>
> You'll be able to access quack via http://10.0.2.15 and auth.domain can
> stay as in your example - auth.domain=10.0.2.15
>
> 1. If that won't help. Might be related to Hazelcast setup.
>
> Lets try the following - replace
>
> whoru.session.provider=ru.greatbit.whoru.auth.providers.HazelcastSessionProvider
> with
>
> whoru.session.provider=ru.greatbit.whoru.auth.providers.InmemSessionProvider
>
> Try to restart the app and run again.
>
> If this will help - you can try returning back Hazelcast provider and
> point it to itself
> hazelcast.members=127.0.0.1
> hazelcast.interface=127.0.0.1
>
> However, if you are running only a single instance if quack service, you
> don't need hazelcast. Inmem provider will do just fine.
>
> —
> Reply to this email directly, view it on GitHub
> <#239 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AZWTTVWCBARX3SAGHTUQ2H3WYSLEJANCNFSM6AAAAAAVCIF5RY>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
Describe the bug
docker-compose -f docker-compose.yml up
(see docker-compose.yml, quack.properties, and quack_startup_log.txt)
To Reproduce
Steps to reproduce the behavior:
point browser to localhost
login as root
create user "bob"
list users
logout from root
attempt to login as "bob"
see session errors for "list users" even though the quack window shows the new "bob" user
see session errors for "login as bob" even though quack said it was created successfully
Environment:
Chrome browser
Ubuntu 22.04
The text was updated successfully, but these errors were encountered: