[JIRA] (JENKINS-61157) Jenkins automatically set entityId as https://jenkins.company.com/securityRealm/finishLogin

25 views
Skip to first unread message

wailoon.tan@dhl.com (JIRA)

unread,
Feb 20, 2020, 12:31:03 AM2/20/20
to jenkinsc...@googlegroups.com
Wai Loon Tan created an issue
 
Jenkins / Bug JENKINS-61157
Jenkins automatically set entityId as https://jenkins.company.com/securityRealm/finishLogin
Issue Type: Bug Bug
Assignee: Ivan Fernandez Calvo
Components: saml-plugin
Created: 2020-02-20 05:30
Environment: saml-plugin 1.1.5
Labels: SAML2 plugin 2.190.1
Priority: Minor Minor
Reporter: Wai Loon Tan

I am configuring SAML2 plugin to connect to Azure Active directory.

In Azure active directory, entity id is created as "jenkins-test".

But when try to logon using SAML, it return this error

 

1) Application with identifier 'https://jenkins.company.com/securityRealm/finishLogin' was not found in the directory 'xxx'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant.

 

2) Upon checking saml-idp-metadata.xml, the entityId is set as "https://jenkins.company.com/securityRealm/finishLogin".

 

3) Nex step, editing saml-idp-metadata.xml to jenkins-test, retry the logon, same error appear, checking back saml-idp-metadata.xml, changes is reverted back to "https://jenkins.company.com/securityRealm/finishLogin".

 

How do we set the plugin to look for "jenkins-test" as entityId instead ?

 

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

wailoon.tan@dhl.com (JIRA)

unread,
Feb 20, 2020, 12:32:02 AM2/20/20
to jenkinsc...@googlegroups.com

wailoon.tan@dhl.com (JIRA)

unread,
Feb 20, 2020, 3:01:02 AM2/20/20
to jenkinsc...@googlegroups.com
Wai Loon Tan commented on Bug JENKINS-61157
 
Re: Jenkins automatically set entityId as https://jenkins.company.com/securityRealm/finishLogin

I found out that you can specify the entityID in Advanced Configuration for SAML 2.0.

Leaving it blank will force Jenkins to use https://jenkins.company.com/securityReam/finishLogin as default entityID, at least that is what i experienced.

kuisathaverat@gmail.com (JIRA)

unread,
Feb 20, 2020, 9:46:02 AM2/20/20
to jenkinsc...@googlegroups.com

kuisathaverat@gmail.com (JIRA)

unread,
Feb 20, 2020, 9:46:03 AM2/20/20
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages