Issues with Basic Auth #360
Labels
bug
Something isn't working
Comments
I've haven't been able to reproduce locally but will take a look.
I have been able to reproduce this and will work on a fix.
We used to have the default route be /incidents/report but at the end of the day we don't really know why a user is hitting the UI (if they don't specify a route). Internally we use a URL shortener to help with guide users (something like
Not today, Dispatch has a limited RBAC facilities that could be expanded but right now we allow folks mostly free-range (except when it comes to restricted incidents). |
|
I added a |
|
Can you see if #371 fixes your redirect issue? |
|
Same problem here. Using basic authentication and getting these errors: My .env looks like that: Log: |
|
Same here (not very useful, I agree). In my case I don't have any data at all (it's a fresh install). And I just can't create any. |
|
@nitzango @onekiloparsec I'm not able to repro locally. Is your database on the latest version? Run |
|
Hi @mvilanova, Not sure if it's related, but now I get the following errors: Thanks for your support! |
Just to make sure, once I run the FYI - Just saw this error on the |
|
@nitzango yes, please check the configuration docs. Let us know if there are any missing env vars. Re: google-auth package error, another user reported the same issue. I'm going to pin rsa to 4.0. |
Thanks @mvilanova - I went over this doc several times, I can't able to understand what is mandatory. I've added In order to get basic auth and before integrating the other plugin (Slack, Gsuite, Jira, etc) - Is it possible to have a running instance? Thanks |
It is possible, yes, but you won't be able to create incidents as we don't have internal substitutes for all plugins yet. See #55 Some of the variables are interdependent, e.g. basic auth requires |
gargrag
added a commit
to gargrag/dispatch
that referenced
this issue
Jun 12, 2020
gargrag
added a commit
to gargrag/dispatch
that referenced
this issue
Jun 12, 2020
mvilanova
pushed a commit
that referenced
this issue
Jun 12, 2020
@mvilanova @kevgliss - I got to a point that no matter what I do, even when starting from a fresh install I get this errors. Steps I did:
|
|
Try setting: instead of: You don't actually need to set the Was there some documentation that made you think it needed to be set? If so, we should make that clearer. |
Thanks @kevgliss. I tried it and result is the same. |
|
Okay, that helps, let me see if I can repo locally. |
|
@nitzango check that you're correctly sending the CORS headers to the Vue app. I encountered the same error as you and determined that the server wasn't sending the CORS headers I had configured with the |
|
@santhoshparepu a few things have changed since this was first reported, please open a new issue and we can debug there. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm trying to get basic auth set up and I have a few issues. I'm not using the dispatch-docker project as I'm trying to deploy to kubernetes.
DISPATCH_AUTHENTICATION_PROVIDER_SLUG=dispatch-auth-provider-basic, I was running into issues with the Vue app not redirecting to /login until I realized I had to setVUE_APP_DISPATCH_AUTHENTICATION_PROVIDER_SLUGat container build time, as well. Even with this,/incidents/reportfails to get Type and Priority because the JWT token is not sent to the API, even though it is present in local storage. It seems the Authorization header isn't being set correctly or in all places?When visiting
/incidents/reportwith a valid token in local storage:visiting
/incidents/reportfor the first time always redirects to/login/loginredirects to the dashboard on successful login instead of back to the report page, which would confuse users who are just there to report issues.Is there a way to separate users who are able to access the dashboard vs users who are able to report incidents?
The text was updated successfully, but these errors were encountered: