I used to rely on the InCommon federated signin for the discourse.
I finally relented and signed up with orcid, though registering with orcid through my institution didn’t seem to work – outcome remains vague.
Nonetheless, I could once again signin to discourse.
Today I followed the link to the community hub, and didn’t recognize InCommon amongst the options, but did think that I could use my access-ci account. That attempt redirected to…orcid. and attempting to login failed.
Perhaps I am the unicorn, and this is something that I need to pursue through my institution. I’ll at least speak within my local HPC team about it. I’d welcome guidance if any is available.
Hi sorry for the delay. I’m not entirely sure what you can do.
From the discourse side I see you can delete your associated accounts in your own profile, but I’m not entirely sure if you have only one association what that may do. If you have multiple associations that may clear up the issue.
Thanks for following up. The situation was resolved when I finally resolved my access-ci signin.
I did not keep careful track of the issues, but over the period of a few weeks, I was able to generate a ‘new’ access-ci based on my institutional login. The matter seemed to be complicated by changes at InCommon.
With a working access-ci login, i was able to associate that to both the discourse, and the separate OnDemand home pages. I was mainly motivated to begin engaging with the affinity groups.
I had used standalone sign-in credentials when joining XSEDE, and carried that over when XSEDE became ACCESS-CI. As ACCESS-CI appears to be the favoured credentials for our two ondemand spaces, my effort to use institutional credentials encountered the friction of my previous stand-alone credentials.
In short, access to discourse and the community pages is now working reliably.