Just updated to Silverblue 41 and now I am having this error when connecting to Fedora project. User and Pass are correct, as I am here 
posting.
Something like “Not possible to create cache for the credentials for this identity”.
I would assume that it is all about permissions… but don’t know where to look at.
Hey, we need more and clearer info
Where do you get this message?
Silverblue is just a way to package Fedora. Which ships Firefox, which likely has some issues here.
But that needs a way clearer description.
What gives this error message, what should it do instead, at what stage does it do that, what happens then.
And since when did this occur, is this really only there since f41?
Sure sorry…
I was on Silverblue 40, and had my fedora project account set at the “online accounts” area at the fedora settings menu.
After updating for Silverblue F41, I started having this error notification, as tehre is an issue in the online accounts interface.
After adding username and pass, it should do a login.
It does not. Weirdly enough, it throws an error message, that due to my choice of accent color (green), looks somehow… positive… :)… it is a good thing that I didn’t log in? Maybe we have to rethink these accent colors on negative messages.
Via the browser I can login with the user and pass.
AS I think you all have this connection configured, opted to post here directly as you might have the same experience and know the fix already.
Great distro, great release, loving it.
J
Thanks, I dont use GNOME and didnt know you could login with your Fedora account in the GNOME settings
What browser do you use?
Added f41, fedora-account-system, gnome, online-accounts
Presently I am using Brave.but I can user the same use/pass on any browser with success.
J
A quinta, 19/09/2024, 22:52, boredsquirrel via Fedora Discussion <notifications@fedoraproject.discoursemail.com> escreveu:
On an F41 Workstation (not Silverblue) fresh install, system up to date, logging into GNOME Online Accounts with the Fedora account is working.
1 Like
Yes I use it but i do not get the error in Gnome. Once a while i get it on the page. But I am not shure if it is this one.
Open the password (seahorse) app and try to find the entry of your fedora login. Click on that an there you can delete the password (seams to be the master password ?!)
When you re login you will be asked for a new one.
I can imagine, that the version change uses different credentials.
- Is the browser using the same password and cached files as on F40?
- Might be that you also have to renew the the login under online accounts (totally remove and recreate)
- Same on accounts.fedoraproject.org change password & change time zone and back to yours. So you will be rewarded with 2 new badges
- And show the badges up here in discourse say hello on: magical-experimental-fedora-badges
If this not works to remove your error, you might make a ticket on infrastructures Pagur.io, asking if they have an idea if it comes from gnome or the account system : https://pagure.io/fedora-infrastructure/issues
1 Like
I would say no…but don’t know where to look
- Might be that you also have to renew the the login under online accounts (totally remove and recreate)
- Same on accounts.fedoraproject.org change password & change time zone and back to yours. So you will be rewarded with 2 new badges
- And show the badges up here in discourse say hello on: magical-experimental-fedora-badges
If this not works to remove your error, you might make a ticket on infrastructures Pagur.io, asking if they have an idea if it comes from gnome or the account system : https://pagure.io/fedora-infrastructure/issues
All the rest is done :D… two new badges in town!!
With this reasoning I expect that you would experience the same issue when connecting other online accounts (e.g. Google, Webdav etc) in Settings → Online Accounts (GOA). Is this the case?
On the other hand, Fedora might have customized GOA in order to provide the option to set up FAS in GOA, hence the behavior might also be different in this particular case.
1 Like
I managed to login with google, but that depends on an browser negotiating the login for the app.
For the rest I don’t have accounts, even my company will not allow me to connect if not a corporate issued computer… and unfortunately they don’t use Fedora.
It really is no issue, as I mostly use fedora accounts via browser… but it was good to have some fuzzy feeling of being part of. 
Best regards…
1 Like
Same here, Fedora Silverblue 41. I cannot add my Fedora account nor a kerberos account, but Online accounts like Google or Microsoft work.
As a side note, one thing I also noticed is that every time I open VSCode, I’m logged out from the Settings Sync option.
I can see an entry in Password for the VSCode but Online Accounts doesn’t even allow me to Sign in.
Did someone make a ticket?
Exact time where it is happen and from where you access.
They might can see something in the log file.
Is this with a microsoft account? Linked with outlook verification?
I got lately a email that they changed per 16th of September something. Week login credentials are not allowed anymore.
I don’t think this is related to the accounts. At least in my case which seems to be the same, the Online Accounts app doesn’t even try to connect. I tried with another Kerberos account not related to Fedora and the same thing happens.
After checking a little bit, I found that for example kbr5-workstation is not installed by default so I installed, and runed a classic kinit against two different servers, both with the same result:
kinit: Connection refused while getting default ccache
No, it’s a GitHub account. Funny thing, Online Accounts works with Microsoft accounts in my system right now.
I only commented this because the issue might be related to how the keyring works. Because the accounts that store a token somewhere (like Google or Microsoft accounts) seem to work fine but the ones that use kerberos or store something in the keyring like VSCode seem to be doing something odd.
I am not really familiar with Gnome development but I tried to debug the GOA application following the instructions and I found that there is an error in the /etc/goa.conf file (is missing):
(goa-daemon:26037): GoaBackend-DEBUG: 10:31:26.403: Failed to load '/etc/goa.conf': No such file or directory
(goa-daemon:26037): goa-daemon-DEBUG: 10:31:26.403: unchanged /org/gnome/OnlineAccounts/Accounts/account_1727180349_0
(goa-daemon:26037): goa-daemon-DEBUG: 10:31:26.403: updating /org/gnome/OnlineAccounts/Accounts/account_1727180349_0 0
And this pointed me to this issue: Authentication failure when setting up new Nextcloud account (#370) · Issues · GNOME / gnome-online-accounts · GitLab
Seems we have an issue in Fedora 41 Silverblue and keyring. I’ll follow it up in the linked issue.
1 Like
For the record: I debugged this a little bit more and finally opened a issue
3 Likes
FWIW, I’m getting this error testing with a fedoraproject.org login:
(process:7420): libgoaidentity-DEBUG: 13:45:49.816: GoaIdentityService: asking to sign in
(process:7420): libgoaidentity-DEBUG: 13:45:49.817: GoaKerberosIdentityManager: signing in identity andyholmes@FEDORAPROJECT.ORG
(process:7420): libgoaidentity-DEBUG: 13:45:49.817: GoaKerberosIdentityManager: don't know if credential cache type (null) supports cache collections, assuming yes
(process:7420): libgoaidentity-DEBUG: 13:45:49.817: GoaKerberosIdentityManager: Error creating new cache for identity credentials: Connection refused
(process:7420): libgoaidentity-DEBUG: 13:45:49.818: GoaKerberosIdentityManager: Waiting for next operation
(process:7420): libgoaidentity-DEBUG: 13:45:49.818: GoaIdentityService: could not sign in identity: Could not create credential cache for identity
On the off-chance this was related to the KEYRING support added last cycle, I hacked that out and the same error still occurs.
1 Like