! Issues with version 1.6 of the plugin

[mjmbischoff]

As indicated in #46 the spec seems to suggest that the scope shouldn't be send when performing an token request as such we won't be sending the scope anymore and thereby fixing the issue with some openid providers that break on this.

As the inverse could also be true: providers no longer working I've created this issue so people can report issues here.

As the only change between 1.5 and 1.6 is not sending the scope it is safe to downgrade to 1.5 and respond to this issue. We will make it configurable in future releases should this be the case.

[uwehdaub]

We are using an inhouse developed OpenID connect compliant Auth server.
This is working fine with 1.5 but not with 1.6, because of the missing scope.
I would prefer to have this property configurable in future releases.

Just stumbled upon this part of the spec:
https://tools.ietf.org/html/rfc6749#section-3.3
Seems that the auth server has some freedom, to which the client has to adapt.

[mjmbischoff]

@uwehdaub Since the plugin is intended to make life easier for ops people and thus aim for max compatibility within reason - we'll add a configuration parameter in the next version.

[talmarco]

I've tried to integrate OpenID authentication with Jenkins and I'm getting the following error:
java.lang.Exception: no field 'preferred_username' was supplied in the token payload to be used as the username
Is this related to one of the changes in this version?

[caryyu]

When is version 1.7/1.6.1 going to be published?

[saikiranp80]

Hi,
How do I logout from jenkins without logging out from global logout ( global logout forces other pages which uses SSO also to be forced logout).

I enabled “Logout from OpenID Provider” and I am not sure what should be the value for "OpenID Provider logout endpoint URL."

is there a way only to logout properly ( by clearing all sessions & cookies) from jenkins when I use open id plugin so that when I click on login it doesn't login automatically from saved session details.

[SIkebe]

I also encountered this issue and reverted it back to 1.5.

We will make it configurable in future releases should this be the case.

I hope it will be released :-)

[michael-doubez]

I'll review the issues as soon as possible. Thanks for the inputs

[michael-doubez]

Closing this long issue.

Reading the question, they should be fixed by newer versions.
If not, please, open a new issue.