See screen shot below:
We are aware of this problem and are working to resolve it.
Now there is a new problem. Is this also known?
FYI I am able to log in to dbGap with my eRA commons ID.
These problems are related to each other (though unrelated to the other issue earlier today). My understanding is that we tried to update the authentication to use a new xml format NIH wants to use. I'm checking with the team now on their progression.
Update: there seems to be a problem somewhere between us and NIH, and we need input from NIH to proceed with troubleshooting. So it's unlikely that this will be solved tonight. I'll update the banner notice when we know more.
Any update? We are blocked!!
We found that the source of the problem was the presence of DOS linebreaks in the certificate provided by NIH. I believe they're testing a fix now so access should be restored soon.
The team confirms that it works now. Al systems functional. The banner will be taken down shortly.
I just tried to access the CA data. I re-linked my account via eRA commons was denied (see image below). I also, as a test, logged into dbGAp to comfirm that my eRA commons id was working.
Hey Megan, I talked about this with Chet this morning -- this is a problem with your dbgap access (not your credentials, the actual authorization status). See the updated banner note.