Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
 
Answered
IDP SSO Questions

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!

Votes Newest

Answers


Hello,

Sorry for the delay on this, Q2 is the IDP by definition alone. In the extension code and your service is defining the relationship and how to login to your external service through the Q2 login. So the answer to your questions is dependent on how you write your code and generate these values.

-Trey

Posted 5 months ago
Edited 5 months ago
Trey Teter
489 × 4 Administrator
109 Views
1 Answer
6 months ago
5 months ago