Hi Franck,
> (In reply to Joe S from comment #0)
> > cifscreds add -u joe fileserver
> >
> > Warning: you have no persistent session keyring. cifscreds keys will
> > not persist after this process exits. See pam_keyinit(8).
>
> This behavior is pretty strange. I'm wondering why in this case cifscreds
> keeps insisting in using the session keyring if it knows that is pointless.
> It could return an error at the very least instead of creating keys that are
> useless. It might have been better to use the user session keyring instead.
>
> That said I agree that user manager instances should have their own session
> keyring
> properly hooked up even though it doesn't sound that useful for user
> services to share keys at a first glance.
It is possible to get cifscreds and pam_cifscreds working as I have done so and
used it like that for MANY months.
I believe the default config is broken and that the systemd-user fix is correct
to fix THAT issue, however, that creates a new issue and breaks a config that
currently does work.
Please see my detailed reply to Fabian. There are 2 RELATED issues going on.