[JIRA] (JENKINS-48030) SAML Azure AD exception

2018-03-15 Thread j...@jamiecon.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jamie commented on  JENKINS-48030  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SAML Azure AD exception   
 

  
 
 
 
 

 
 I have just rechecked the value and it is the same now as it was on the 6th of this month. Hope this helps  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48030) SAML Azure AD exception

2018-03-06 Thread j...@jamiecon.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jamie commented on  JENKINS-48030  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SAML Azure AD exception   
 

  
 
 
 
 

 
 Ivan Fernandez Calvo I see. I have made a note of the value for my system and I will check back every few days to see if it has changed. I'll report back in a week or so I guess?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48030) SAML Azure AD exception

2018-03-06 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-48030  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SAML Azure AD exception   
 

  
 
 
 
 

 
 I do not have all the context but the first is tenant-specific and the second one is tenant-independent, I am not sure if this token can change or not in the first choice.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48030) SAML Azure AD exception

2018-03-06 Thread j...@jamiecon.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jamie commented on  JENKINS-48030  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SAML Azure AD exception   
 

  
 
 
 
 

 
 Ivan Fernandez Calvo My configuration also uses a GUID, in the first format style. Not my area but isn't this feature something to do with if you are, say, building a hosted application which allows multiple Azure AD users to utilise it?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48030) SAML Azure AD exception

2018-03-05 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo edited a comment on  JENKINS-48030  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SAML Azure AD exception   
 

  
 
 
 
 

 
 [~shawnparslow] both are C&P from https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-federation-metadata#entity-id so  they  should be not valid values.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48030) SAML Azure AD exception

2018-03-05 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-48030  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SAML Azure AD exception   
 

  
 
 
 
 

 
 Shawn Parslow both are C&P from https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-federation-metadata#entity-id so should be not valid values.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48030) SAML Azure AD exception

2018-03-05 Thread shawnpars...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shawn Parslow commented on  JENKINS-48030  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SAML Azure AD exception   
 

  
 
 
 
 

 
 My configuration uses the Azure GUID in the entityID: entityID="https://sts.windows.net/12345678-1234-1234-1234-123456abcdef/"  FYI, this GUID represents the Directory ID of your Azure Active Directory in your subscription that you are authenticating against (you might want to scrub it from your comment).    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48030) SAML Azure AD exception

2018-03-05 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo edited a comment on  JENKINS-48030  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SAML Azure AD exception   
 

  
 
 
 
 

 
 I am  documented  documenting  how to configure Azure service to work with the plugin and there is something in the documentation about the Entry ID in the Idp Metadata XML that claim my attention there are two formats* entityID="https://sts.windows.net/72f988bf-86f1-41af-91ab-2d7cd011db45/"* entityID="https://sts.windows.net/{tenant}/ " the first one seems that could change with the time and the second one seems to be always the same, Could you check the Entry ID type you use in your IdP Metadata XML?https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-federation-metadata#entity-id  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48030) SAML Azure AD exception

2018-03-05 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-48030  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SAML Azure AD exception   
 

  
 
 
 
 

 
 I am documented how to configure Azure service to work with the plugin and there is something in the documentation about the Entry ID in the Idp Metadata XML that claim my attention there are two formats 
 
entityID="https://sts.windows.net/72f988bf-86f1-41af-91ab-2d7cd011db45/" 
entityID="https://sts.windows.net/ {tenant} / 
 the first one seems that could change with the time and the second one seems to be always the same, Could you check the Entry ID type you use in your IdP Metadata XML? https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-federation-metadata#entity-id  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.