Skip to main content
For example, you can use embed URL parameters to:
  • Specify user content roles
  • Assign connection and model roles to users
  • Control the look and theme of your embedded application
  • Apply user attributes to users

​
Providing parameters

How parameters are provided depends on the type of SSO setup your embed implementation uses:
  • In standard SSO embed, parameters are passed as URL query parameters: 
    https://omni.blobsrus.com/embed/login?contentPath=%2Fmy&externalId=artiste1322&name=Blob+Ross&nonce=7RR6BdkQ8FgXf2FHABLFhWTebflsWya2&signature=VwmHh5ygv35i0Zc8mTiT6ugRnzqwBLfEP83ZDh6pfVE&entity=Happy+Trees&connectionRoles=%7B%7D&entityFolderContentRole=EDITOR&preserveEntityFolderContentRole=false
  • In 2-step SSO embed, the majority of these parameters are included as a JSON payload in the POST /generate-session request:
    POST /api/unstable/embed/sso/generate-session
    curl -X POST 'https://omni.blobsrus.com/api/unstable/embed/sso/generate-session' \
-H 'Authorization: Bearer <YOUR_API_KEY>' \
-H 'Content-Type: application/json' \
-d '{
  "contentPath": "/my",
  "externalId": "artiste1322",
  "name": "Blob Ross",
  "entity": "Happy Trees",
  "entityFolderContentRole": "EDITOR"
}'

​
Available parameters

Refer to the Embed URL parameters reference for a complete list of parameters and examples.