ContributionsMost RecentMost LikesSolutionsSSO for multiple Orgs We’ve got SSO via SAML / Azure AD setup for all of our orgs but we can only successfully login via SSO for one of the Orgs (lets call it ‘org c’). In Azure we’ve setup 3 separate apps , one for each of those orgs (with different entity/reply/logout urls). I can see from previous posts that we must use the same metadata file for all orgs so i’m using the metadata file from/for ‘org c’ on ‘org a’ and also ‘org b’. Whilst i can login via sso successfully on ‘org c’ i get an error stating ’ SAML Response Invalid’ when attempting to login to ‘org a’ and ‘org b’. Have you got multiple orgs? If so, did you experience the same issue ? How did you set it up on the Azure side? Re: SSO login issues Hi @Petrica, thanks for getting back to me. More specifically, i was looking to see what issue you found in your idm file? Which part of the file was incorrect? Re: SSO login issues @Petrica, what exactly was the problem with the metadata idm file please? I am experiencing a similar issue. Have tried using the same meta file as another org but that results in “Single Sign On authentication failed.SAML Response is invalid” Re: Soap Execute Reference is not allowed in prolog error Found the resolution in Passing XML to SOAP Execute Snap. #evaluate($xml) is what goes into the customised envelope Soap Execute Reference is not allowed in prolog error Hi All, When creating a pipeline with a soap execute, i’m getting the error “Failure: An error occurred while parsing the request document, Reason: Reference is not allowed in prolog., Resolution: Please verify the validity of the XML document” I’m using a adding a list of ids to an array $users . Then i use the xml generator to pass through the working xml (as per soapui) which references that $users array into the soap execute. Soap execute custom envelope only contains ‘$xml’. The resulting error is “Failure: An error occurred while parsing the request document, Reason: Content is not allowed in prolog., Resolution: Please verify the validity of the XML document”. I guess the question is, how do i reference an array or field within the customised envelope of the soap execute snap? SolvedRe: Active Directory Search snap does not search arrays as expected @robert_parks we have logged this as a bug with Snaplogic support as it is a bug. We awaiting on a update on the cause and fix. It may be worth doing the same from your side to help raise the priority and for them to understand the impact. Active Directory Search snap does not search arrays as expected Using the Active Directory Search Snap, when specifying an AD group, i expect the search to look through the array of groups for each ‘user’ / ‘mail’ but it does not. Instead, it looks at the first ‘memberOf’ value for each email address rather than searching the full array. For example, if the following users exist and linked to the groups below: myself@company.com,[GroupA,GroupB,GroupC,GroupD] yourself@company.com,[ GroupA,GroupB,GroupC,GroupD] When we do a search for all those on Group C, no results will return. When we do a search for all those on GroupA, all the above emails will be returned. Has anyone experienced the same and what was the workaround?