Using Software Model Subscription Condition with SSO Applications
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2022 08:11 AM
We're using SAM Pro with SaaS License Management integrated with Azure AD for license management, spend, etc. We have quite a few SSO Applications that encompass multiple AD groups for granting different license types (e.g. reader, writer, admin, etc.). Each SSO Application is associated with a Software Model and then we have one or more Software Entitlements associated with each Software Model for tracking spend, over and under utilization, etc. Back when we were on Rome, there was no way to associate different license costs with different license types for subscriptions associated with SSO applications. However, San Diego introduced the "Subscription Condition" field on the Software Model, which we can use to limit what the Software Model associates with. In the "Subscription Condition" field, we can build conditions against the SSO Application role/group. I've created a few Software Models and set the Subscription Conditions to apply to different AD groups for one of our SSO Applications but I'm not sure how we associate those Software Models with the SSO Application. Does the association happen automatically somehow? Is there something else I need to do to associate the multiple Software Models with the SSO Application? Thanks in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2023 02:51 AM
Hi Rithika,
I don't need you to edit it just as long as you have it in your list view is fine.
For the subscriptions that are licensed and viewonly for this application is that field populated with anything at all?
Thanks,
James
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2023 10:51 AM
yes, with the software model - ABC model (product - ABC, version - anything, edition - anything) listed in my clarification previously.
This is the model that is added against the SSO application in the SSO integrations.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2023 02:22 AM - edited 07-14-2023 02:26 AM
So is it different for your licensed and viewonly subscriptions or the same? That's what i'm trying to get at.
ps. I would make sure in your model you set a "condition name" so you can easily identify which is which