-
Notifications
You must be signed in to change notification settings - Fork 562
Contributor License Agreement signing broken #731
Comments
Hi, The certificate on https://cla.dotnetfoundation.org/ seems to be working for me; what is pointing you to cla2? |
Yeah, on https://cla.dotnetfoundation.org/ the certificate is working. However. I'm not able to manage to sign something there. My only Option is to click on Administrator Sign In. Doing so, results in GitHub requesting me to allow my account usage. After confirmation I'm redirected back to https://cla.dotnetfoundation.org/. Thats all. I found https://cla2.dotnetfoundation.org/ on some places mentioned therefore I tried that one as well. For example on: |
The whole DocuSign part enpictured there is missing for me, on https://cla.dotnetfoundation.org/ (Tried Chrome, Edge, IE, Opera on two devices) |
There's no end-user access to the CLA. What are you trying to do? CLA2 is old and not used. In general, if the CLA needs to be signed, the bot will put a comment in the PR with a link to click. It'll then update the status afterwards. |
I wanted to post an issue to AutoMapper I could find no mention of an restriced target audiance of the CLA. And how do you define an end user? |
Just hit the same issue myself. If cla2 host is not used anymore .NET foundation should make a redirect to cla or just make a static page on cla2 with explanation what's going on and how to sign CLA now. cla2 link is used in dozen of projects on GitHub so just dropping the host without explanation is not acceptable. |
Hello,
I want to sign the Contributor License Agreement. However one site is not working, the other has a corrupt SSL cert. I'm not sure, where to report this, but this is the most appropriate place, I could find.
Not working (for me):
https://cla.dotnetfoundation.org/
Certificate error:
https://cla2.dotnetfoundation.org/
The text was updated successfully, but these errors were encountered: