I tried logging in on the local development server but have been persistently getting this error. I tried it even in incognito but the same error came up.
<img alt="Screenshot_from_2019-02-28_20-00-32.png" src="/fedora-commops/fedora-happiness-packets/issue/raw/files/4ee5c60ff786660628d6a4735f3bdbf9b05e7315a318e9f6002e72e4656c4150-Screenshot_from_2019-02-28_20-00-32.png" />
Metadata Update from @jflory7: - Issue priority set to: needs review (was: awaiting triage) - Issue tagged with: bug, needs info, type - summer coding
@varsha97 I cannot reproduce this. To help debug, try regenerating the client secrets. Delete the client_secrets.json file and run the generate_client_secrets.sh script again.
client_secrets.json
generate_client_secrets.sh
Once you have done that, please explain the following:
fedora-happiness-packets doesn't directly handle authentication, it relies on Ipsilon to authenticate with Fedora Account System (FAS) accounts. This may not be an issue with fedora-happiness-packets but I don't know yet.
Metadata Update from @jflory7: - Issue assigned to varsha97 - Issue priority set to: waiting on assignee (was: needs review)
@jflory7 I tried generating the client secrets with generate_client_script.sh again followed by docker-compose up and accessing the local server. I tried to login and the same error came up again.
generate_client_script.sh
docker-compose up
Since you are not able to reproduce, is it possible that there is some problem with the fedora account that I am trying to login with? As in, it's missing some privileges which I might not have or something similar.
@varsha97 Please share the docker and docker-compose version you are using. Also, you need to build the docker image again. Run docker-compose up --build and follow each step of the setup documentation and give a detailed answer as requested above.
docker
docker-compose
docker-compose up --build
Docker version 18.09.0, build 4d60db4 docker-compose version 1.21.2, build a133471 @shraddhaag
I tried running the test suite with ./t after accessing the docker shell and many of the tests are also failing. Is that expected?
./t
Hi @varsha97 , can you give me the details of what system (OS) are you using ..??? Also, did you run chmod -x ./generate_client_secrets.sh before ./generate_client_secrets.sh
chmod -x ./generate_client_secrets.sh
./generate_client_secrets.sh
I am using ubuntu 18.04 And yes, I tried changing the permissions and then generating the secret keys but to no avail.
I also have the same problem but mine is bringing a different error saying (BAD REQUEST invalid redirect uri.)
my docker and docker compose is working perfect plus my reddit is also fine
@shraddhaag I HAVE DONE WHAT YOU TOLD ME AT ISSUE #109 . KINDLY CHECK THE THE SCREENSHOT I RECORDED
Kindly anyone to check this link below and tell me where i could be wrong
https://youtu.be/VMKGUJGKbbU
@shraddhaag ALSO CHECK THE STATUS RECEIVED FROM THE TERMINAL UPON CLICKING THE BUTTONS
<img alt="Auth_status_report.png" src="/fedora-commops/fedora-happiness-packets/issue/raw/files/b5dec88a8acef8c27a5cc190db9476e7557bb34ffff3b0b22fea57597cab17e9-Auth_status_report.png" />
Since you are not able to reproduce, is it possible that there is some problem with the fedora account that I am trying to login with?
@varsha97 The error you have looks like rate-limiting. Maybe this is an issue if you are on a public WiFi network when you are testing. Is it possible for you to try this again on a different network?
If this does not change then, we'll need to follow up with folks in #fedora-apps on Freenode for help.
#fedora-apps
Hi @feisal, please do not write in all capital letters. It is not necessary. I suggest reading some do's and dont's from the Google Summer of Code blog.
@feisal The issue you are facing is different and not on-topic to this ticket. Like I asked in #109, please reach out to the CommOps team for support instead of commenting in unrelated tickets.
@jflory7 ok i have reached out to them through Linkedln
Thanks and i am sorry for writing in capital letters.. my intention was i wanted to emphasize it so the reader knows the exact problem.
No worries – I figured your intentions were good. However, please avoid doing it in the future. Thanks. :smile:
I just came across this: Login on 127.0.0.1:8000 returns 400 - Bad Request. Invalid redirect_uri but has full functionality when navigating to localhost:8000. This is due to "redirect_uris": ["http://localhost:8000/oidc/callback/"] in client_secrets.json.
127.0.0.1:8000
400 - Bad Request. Invalid redirect_uri
localhost:8000
"redirect_uris": ["http://localhost:8000/oidc/callback/"]
@varsha97 @feisal Maybe try this out and see if your errors get resolved by this?
I think the issue @varsha97 had is different. From the screenshot, it looks @varsha97 is accessing the site at localhost:8000. Because the error message says max tries are exceeded, I wondered if the issue was something to do with rate-limiting.
I am curious to know if this issue is reproduced when changing wireless networks. Otherwise, I am a little stuck on how to debug, and we'll likely need to ask some others in Fedora Infra for help.
Oh yes, localhost couldn't have been the problem. @varsha97 Could you please change your connection and retry and tell us your findings?
localhost
Hope this has been solved. If not try to use localhost:8000 instead of http://127.0.0.1:8000
Hi, per the contributing guidelines, I'm going to close this ticket as insufficient data since it has been almost two weeks since follow-up.
@varsha97, if you need help or continue to face this issue, let us know. :)
Metadata Update from @jflory7: - Issue close_status updated to: insufficient data - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.