Per the instructions given to our team (copr-team), we should use:
https://id.fedoraproject.org/saml2/SSO/Redirect?SPIdentifier=urn:amazon:webservices&RelayState=https://console.aws.amazon.com
... that should allow us to authenticate using Ipsilon, and redirect to AWS web-UI. But at the moment I'm getting:
500 - Internal Server Error Ipsilon encountered an unexpected internal error while trying to fulfill your request. Please retry again. If the error persists, contact the server administrator to resolve the problem.
I just tried the link and it worked, could you try again? I have noticed this sporadic error before myself.
It worked for me now in private tab, but didn't work at the time of reporting this. Normal (firefox) tab still doesn't work .... even after clearing all cookies for id.fedoraproject.org.
I suspect this may be https://pagure.io/ipsilon/issue/343
As mentioned by pingou this apppears to be an issue upstream
Metadata Update from @mobrien: - Issue close_status updated to: Upstream - Issue status updated to: Closed (was: Open)
Could you check if you still have the issue?
Cf https://pagure.io/ipsilon/issue/343#comment-674766 for details
Works fine. Thanks.
It happened again today: https://pagure.io/fedora-infrastructure/issue/9301
Metadata Update from @praiskup: - Issue status updated to: Open (was: Closed)
I think I have the same issue now, except for the "private" tab in firefox doesn't work-around it now.
@praiskup I've deleted the pod I saw the traceback on, can you try again? (I was able to log in on bugzilla.rh.c here)
On Thursday, November 26, 2020 2:56:12 PM CET Pierre-YvesChibon wrote:
Works fine now. Thank you.
So same bug but fixed here again.
I know we're planning on moving ipsilon back onto a VM, maybe it'll help with this issue!
Metadata Update from @pingou: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Sorry for reopen, but I experience the same problem today.
I am classifying this for the sake of the ticket, but I think we are unable to 'fix' it currently.
Metadata Update from @smooge: - Issue tagged with: authentication, high-trouble, medium-gain, ops
Metadata Update from @smooge: - Issue close_status updated to: Will Not/Can Not fix - Issue status updated to: Closed (was: Open)
But this blocks us from accessing the AWS web console. If this can not be fixed, do we have a work-around?
We can fix it, give me a few
Alright, should be fixed now :)
Metadata Update from @pingou: - Issue status updated to: Open (was: Closed)
Issue status updated to: Open (was: Closed)
Issue status updated to: Closed (was: Open) Issue close_status updated to: Fixed
Login to comment on this ticket.