Hey all, I've been reading and reviewing the SSO extension example for an IDP SSO - https://docs.q2developer.com/tutorials/sso/index.html. I have a couple of questions: 1. Per the vendor documentation, they are going to provide a SAML SP Metadata XML file to be loaded into Okta or some other service. We don't have that. In my reading, Q2 is the identity provider. Am I reading that correctly? I'm assuming this xml file has the items that would be the `VENDOR_CONFIGS` in the example code. `ACS_URL, SP_ENTITY_ID, TARGET_DESTINATION` 2. IDP Entity ID - the documentation has a placeholder value. How is this created? 3. Information I provide to the vendor - SSO Url, Entity ID, Certs (pub key). Is the SSO url the same one used in the deeplinking example? Is the vendor ID the same ID in deeplink url. I'm just trying to line up items and steps in the vendor docs to the SDK example and docs. Thanks!

Hey all, I've been reading and reviewing the SSO extension example for an IDP SSO - https://docs.q2developer.com/tutorials/sso/index.html. I have a few questions: 1. Per the vendor documentation, they are going to provide a SAML SP Metadata XML file to be loaded into Okta or some other service. We don't have that. In my reading, Q2 is the identity provider. Am I reading that correctly? I'm assuming this xml file has the items that would be the `VENDOR_CONFIGS` in the example code. `ACS_URL, SP_ENTITY_ID, TARGET_DESTINATION` 2. IDP Entity ID - the documentation has a placeholder value. How is this created? 3. Information I provide to the vendor - SSO Url, Entity ID, Certs (pub key). Is the SSO url the same one used in the deeplinking example? Is the vendor ID the same ID in deeplink url. I'm just trying to line up items and steps in the vendor docs to the SDK example and docs. Thanks!