openSUSE admin

crameleon wrote in #note-1:

Hi,

that is rather interesting - your IDP profile does have a givenName set, and it is correctly propagated to Progress.
Are you authenticating with a user other than ybonatakis ?

No I dont.

Given the comment https://progress.opensuse.org/issues/9792#change-789348 (and the same comment in some other tickets) I'd guess that it works now.

BTW: I'd be surprised if example.com would explain what the SLO period is ;-) - and ideally please also tell your bot not to add reminders on resolved tickets.

problem still persists I would say. At least in most of the cases

Sorry, but I cannot help without knowing what exactly you are trying to do.
The error in your request is implemented to be returned on the first login of a user to progress.opensuse.org if the first name is not populated. I do not know a code path which would return it on subsequent logins where the first name is already populated (as is the case in your profile, both in Redmine and in IDP):

https://build.opensuse.org/projects/openSUSE:infrastructure:redmine/packages/redmine-openid_connect/files/suse-idp-missing-firstname.patch?expand=1

Hence, please provide steps I can follow to reproduce the issue.

Go to https://progress.opensuse.org/issues/137885 for example.
As logged in user with ybonatakis I edit the URL and add .json
I expect https://progress.opensuse.org/issues/137885.json render and show the context but instead it redirect me to login and once again after enter my credentials i see the error.
Actually, it shows that the page doesnt work first and then i see
This tool requires your account to provide a first name. Consider raising a request in https://progress.opensuse.org/projects/opensuse-admin/issues (or https://sd.suse.com if you are an employee) to get a first name added to your profile. In the meanwhile, your first name on progress.opensuse.org will be set to "Anonymous". Click "Sign in" to confirm.Email cannot be blank. Login cannot be blank. Last name cannot be blank. and
Invalid user or password Try logging in with another account

Thanks, I can confirm the redirection issue when trying to access issues with .json through the web browser.
It certainly is not quite right, though it seems to work fine when used with scripting tools, which should be what most users use the .json route with.

Do you observe any issues when trying it with curl?
You can generate an API key in https://progress.opensuse.org/my/account and then use it like the following:

curl -H 'Content-Type: application/json' -H 'X-Redmine-API-Key: <your secret key>' https://progress.opensuse.org/issues/137885.json