Hi, Im following the steps from the following link https://community.cyberark.com/s/article/KB-8625-How-to-update-application-metadata-to-use-an-Idaptive-URL-suffix-of-idaptive-app

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Hi, Im following the steps from the following link https://community.cyberark.com/s/article/KB-8625-How-to-update-application-metadata-to-use-an-Idaptive-URL-suffix-of-idaptive-app

L1 Bithead

and in part 1 it details how to run the report of apps that are currently using the Centrify url, after I run the report it shows all the apps in our environment but on some of them it is showing the correct URLs i.e my.idaptive.app so im not sure why its still showing up on the report? As you can see from the below image, web hr is showing on the report as still having the Centrify url but as you can see the links are showing as the my.idaptive.app

 

could you please clarify why these apps are still showing up on the report? Is it because we haven’t updated our main site url to my.idaptive yet? We are using pico.my.centrify.com still, should we update this first and then the apps?

 

Field_Content_versions_oct20__0682J00000BtPZJQA3.png

11 REPLIES 11

L2 Linker

Thank you for the update.

 

If you are configuring the application with metadata, after you have followed the KB-8625 to update the url into idaptive.app url, you may need to:

(1) Download the metadata after changes of url using

(2) Import the new metadata to SP's configuration page

*(3) After (2), Download the metadata from SP, and upload in the app settings.

After performing the above 3, the url inside the SAML response should not be using the old centrify url.

 

For step3, suppose you do not need to re-upload the latest metadata from SP to Idaptive again. 

I mentioned this (to re-uploaded the metadata in Idaptive again) because for some SP it requires this step after we have made changes on SP's setting. 

We also included this reminder in the KB-8625, and it actually depends on the SP (you may need to check with the SP to ensure if it is needed).

 

For most of the cases, you do not need to re-upload it on Idaptive unless you found from the report the launching of application still using centrify.com, then you may wish to try re-uploading the new SP metadata to IDaptive.

L1 Bithead

Field_Content_versions_oct20__0682J00000C45l0QAB.pngHi paul,

 

i tried this and it didnt work im receving the below error, any chance we can do a screenshare and i can go through it with you?

 

Kind Regards,

Conor

L1 Bithead

Hi Paul,

 

im trying to update all our apps but for example heres the meta data from slack

 

SAML 2.0 Endpoint (HTTP) - https://aad0021.my.idaptive.app/applogin/appKey/d15ebe0f-235d-4b7a-8cfb-b47893a8ae31/customerId/AAD0021   Identity provider issuer https://aad0021.my.idaptive.app/d15ebe0f-235d-4b7a-8cfb-b47893a8ae31   Public certificate Centrify Customer AAD0021 Application Signing Certificate (), expiring on1st January 2039 (edit)   -----BEGIN CERTIFICATE----- MIIDDzCCAnigAwIBAgIPG/eC3ca7tkSd2vm8gHA2MA0GCSqGSIb3DQEBCwUAMCQx IjAgBgNVBAMMGUNlbnRyaWZ5IEN1c3RvbWVyIEFBRDAwMjEwHhcNMTcwNzEzMTcz ODQ3WhcNMzkwMTAxMDAwMDAwWjBEMUIwQAYDVQQDDDlDZW50cmlmeSBDdXN0b21l ciBBQUQwMDIxIEFwcGxpY2F0aW9uIFNpZ25pbmcgQ2VydGlmaWNhdGUwggEiMA0G CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCH3AglbtPeP5qWuuttS7gpCOBAgeo7 uds0ia8Cd2EdWcDTISDEgcsuBhpv+YuA/N3D3MDDOM/d+iwUaYupm49E2CjBfQFJ EFH6URfTdzItUJId9WNWdDdlhrXNTOP5AuxPPOOJ1yrNNpmIb+9k93LwVKJOPgtp M652ZgxlI7ugvcmwyN/UcqcxcKh3+afH0TbBtCXfWotsvv0umpTGNEDXS0/m6y1e lsUcLLptgnVNRo3DRyTuDKjCsCOfy7Grjng3e/anFUddXb4t8F/JwBxCIQt/oYiK f4/+7EwYFEx5+clI5pjcn9OOcl9cm1l7OU8nVHWdpTCZgdMrcs9u6zUzAgMBAAGj gZ4wgZswEwYKKwYBBAGCpnABCQQFDAMxLjAwFwYKKwYBBAGCpnABAwQJDAdBQUQw MDIxMB8GA1UdIwQYMBaAFKDsmEHSnSThQJsPlpflA66hx7wDMB0GA1UdDgQWBBR/ 8Cq3peBXMTLXkI6La9DG3eTi4DAOBgNVHQ8BAf8EBAMCBaAwGwYKKwYBBAGCpnAB BAQNDAtBcHBsaWNhdGlvbjANBgkqhkiG9w0BAQsFAAOBgQB2Q3026YuTm1zdLeSj E3GjsGoe3S7YdY+AUsUK7NKey1QlWwWD8UkuzAiTl8bfROa320kQXexqR7crOuoH KhcPJIo/oTr+gqBH0vRLvkOToc75hQo3XvoB2nNUkv37ffGeBeWdjvO4iC/qxtpv AXZ5AzYXIQpUV6RloM5cQsSWKQ== -----END CERTIFICATE-----

 

L1 Bithead

Hi Paul,

 

i cant seem to download any of the metadata from our vendors sites, only salesforce, are any of your other clients experiencing the same issue as myself?

below is the list of apps we use, ive attahced a list of salesforce metadata

Salesforce

Zoom

Office 365

Zscaler

JIRA

WageWorks

WebHR

BambooHR

Aha!

Thomson Reuters

WebEx

Slack

Cisco Spark

Concur - Corvil

Small Improvements

Confluence

Docebo eLearning

Device42

Concur | Concur Solutions

AWS Corvil

SolarWinds Orion

Zscaler - admin

L1 Bithead

<?xml version="1.0" encoding="UTF-8"?><md:EntityDescriptor xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" entityID="https://picotrading.my.salesforce.com" validUntil="2030-10-19T13:18:11.917Z" xmlns:ds="http://www.w3.org/2000/09/xmldsig#">

<md:SPSSODescriptor AuthnRequestsSigned="true" WantAssertionsSigned="true" protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">

<md:KeyDescriptor use="signing">

<ds:KeyInfo>

<ds:X509Data>

<ds:X509Certificate>MIIGDDCCBPSgAwIBAgIQDq5fq/a4r5D1pwYE//HWBzANBgkqhkiG9w0BAQsFADBN

MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMScwJQYDVQQDEx5E

aWdpQ2VydCBTSEEyIFNlY3VyZSBTZXJ2ZXIgQ0EwHhcNMjAwNjA0MDAwMDAwWhcN

MjEwNzA5MTIwMDAwWjBUMQswCQYDVQQGEwJJRTEPMA0GA1UEBxMGRHVibGluMRcw

FQYDVQQKEw5Db3J2aWwgTGltaXRlZDEbMBkGA1UEAxMSc3VwcG9ydC5jb3J2aWwu

Y29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqyTFI5IxtAJWFSii

sDBvnFP7B2skd6V8ZZcMOItU8gBNMOa3Nwf+QJIPRg6N7BMcsl/aQRmQQFTSndiA

en2pmoUWFXZnnsYh7I/QtFkO3GaBw5pM0ocyQ2mC0lX9014BHvpJIcfaClgCPge2

VL0M/t/v7eUBk141oFqJWbLQWWsqF3bchuQQnyiE0ypKg4/0Uv6R0FajRr6PFMgp

12bEnN1rwLsEtkuSYQhA+6Kw/VRq1I40wHdIjEAfUfdMbYEaHCm4NkFXiLENiAfP

/9AptYW+In1Cokup1X5139Rs0NKsNDKhrAA/uVllrdo/L+EQ5HmhY1If9xkkuvav

ANMmLwIDAQABo4IC3zCCAtswHwYDVR0jBBgwFoAUD4BhHIIxYdUvKOeNRji0LOHG

2eIwHQYDVR0OBBYEFPvXMuXFUdsgMokX9Az0jOJnYuxkMB0GA1UdEQQWMBSCEnN1

cHBvcnQuY29ydmlsLmNvbTAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0lBBYwFAYIKwYB

BQUHAwEGCCsGAQUFBwMCMGsGA1UdHwRkMGIwL6AtoCuGKWh0dHA6Ly9jcmwzLmRp

Z2ljZXJ0LmNvbS9zc2NhLXNoYTItZzYuY3JsMC+gLaArhilodHRwOi8vY3JsNC5k

aWdpY2VydC5jb20vc3NjYS1zaGEyLWc2LmNybDBMBgNVHSAERTBDMDcGCWCGSAGG

/WwBATAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy5kaWdpY2VydC5jb20vQ1BT

MAgGBmeBDAECAjB8BggrBgEFBQcBAQRwMG4wJAYIKwYBBQUHMAGGGGh0dHA6Ly9v

Y3NwLmRpZ2ljZXJ0LmNvbTBGBggrBgEFBQcwAoY6aHR0cDovL2NhY2VydHMuZGln

aWNlcnQuY29tL0RpZ2lDZXJ0U0hBMlNlY3VyZVNlcnZlckNBLmNydDAMBgNVHRMB

Af8EAjAAMIIBAgYKKwYBBAHWeQIEAgSB8wSB8ADuAHUA9lyUL9F3MCIUVBgIMJRW

juNNExkzv98MLyALzE7xZOMAAAFyfwLw5QAABAMARjBEAiBtnzC9/ldnz+t2uH1m

kaiDHreLh3W4PpvmelptVj8uuAIgN8pPhD6n9UhQnnMzAdm83M2004NHhfmGflVp

d1VnGakAdQBc3EOS/uarRUSxXprUVuYQN/vV+kfcoXOUsl7m9scOygAAAXJ/AvED

AAAEAwBGMEQCIANUCAW0r1Uu8KnjoA/ULjrvu5h+sUTNs5sETo3XPBcPAiBKckdk

hydruMQkdtRM8gVr1DWgVMKlI9zjCkYx5b6V0TANBgkqhkiG9w0BAQsFAAOCAQEA

lnKhkZqWdSu73VIHVCHRv4Go5xj9NKF7w1P1HD5JhK3Hi6192EFskTi0Z8kqklhV

bmyj/LeQB6KJOXBK8wuz6hSHzk3BB0jOf7r5FI7vB63q+vTQ0TrK6x9mK4CCRnub

/ppVxt9CTo7eh1r+f89KdK+/nKEuv1zBhnxohxyZBpyCXRvyFdhi2b18f4TcxG+8

F9Fyz4ebDyhb/lWZqqBVAzXoO4sWpIC+NGFbcFEDhaLdPTsv2R7h5JjGXTiGGhto

3UtfTUDuvt5YzoYAXDc3sLS/ah4Bjcww1o+KP1MyO9UGfqmm9LE0ssROLvmygOfe

BYIkrbdbICZVmAzoFzQpTg==</ds:X509Certificate>

</ds:X509Data>

</ds:KeyInfo>

</md:KeyDescriptor>

<md:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://picotrading.my.salesforce.com/services/auth/sp/saml2/logout"/>

<md:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="https://picotrading.my.salesforce.com/services/auth/sp/saml2/logout"/>

<md:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://corvilcommunity.force.com/CorvilDevTest2/services/auth/sp/saml2/logout"/>

<md:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="https://corvilcommunity.force.com/CorvilDevTest2/services/auth/sp/saml2/logout"/>

<md:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://support.corvil.com/services/auth/sp/saml2/logout"/>

<md:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="https://support.corvil.com/services/auth/sp/saml2/logout"/>

<md:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://corvilcommunity.force.com/support/services/auth/sp/saml2/logout"/>

<md:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="https://corvilcommunity.force.com/support/services/auth/sp/saml2/logout"/>

<md:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://support.pico.net/services/auth/sp/saml2/logout"/>

<md:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="https://support.pico.net/services/auth/sp/saml2/logout"/>

<md:NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</md:NameIDFormat>

<md:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://picotrading.my.salesforce.com?so=00D200000000DgE" index="0" isDefault="true"/>

<md:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://corvilcommunity.force.com/CorvilDevTest2/login?so=00D200000000DgE" index="1"/>

<md:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://support.corvil.com/login?so=00D200000000DgE" index="2"/>

<md:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://corvilcommunity.force.com/support/login?so=00D200000000DgE" index="3"/>

<md:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://support.pico.net/login?so=00D200000000DgE" index="4"/>

</md:SPSSODescriptor>

</md:EntityDescriptor>

 

L2 Linker

Hello Conor,

 

Thank you for the inquiry.

 

We actually depends on the SP for the update of url - some applications we do not need to uploaded their latest XML to our end. We have mentioned in the KB:

"Some Service Providers require the metadata to be updated on our end after providing these changes. Please check with your Service Provider if this is needed for your app."

 

We do not have heard from other customers with similar issue reported. In your list we can see there is Office365, which the steps need to be taken for this app is somehow different than other application: You may refer to the part "2. How to validate and update Office 365" in the KB-8625

https://community.cyberark.com/s/article/KB-8625-How-to-update-application-metadata-to-use-an-Idaptive-URL-suffix-of-idaptive-app#one

 

We will advise you to run the report "Apps using Centrify Url" again, after that check to configure the applications on the report one by one. Follow the steps we mentioned in the KB either configure it with metadata/ by manual configurations, which depends on SP's requirement.

 

Please kindly log the case on the support ticket as we are following up on that: (01887594).

 

Thank you for your help.

 

Best regards,

Paul Lam

L1 Bithead

Hi Paul,

 

ive followed the KB word for word and im still running into errors, zoom is updated to idaptive.app on both ends and were still running into the issue that its appearing in the report, can we arrange a screenshare so i can show you

 

Kind Regards,

Conor

L1 Bithead

Hi Paul im available from 9-3.30 if you have any availability then

L1 Bithead

im in ireland so GMT+1

L1 Bithead

perfect im free then, do you have a meeting link for me?

L2 Linker

Thanks for joining in the meeting and discuss with us the issue two weeks before.

During the call, we have looked into the issue and recommended you to update the url for each issue again and how to run the report. We also mentioned the issue could be related to tenant url change. We are awaiting updates but this should be working fine now.

  • 450 Views
  • 11 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!