cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
AamerSharif
By Level 9 Flexeran
Level 9 Flexeran

Summary

We are delighted to announce Flexera One ITAM SOAP API integration has been transitioned to Flexera One Identity and Access Management (IAM) from Flexera AGW (legacy identify provider). Now Flexera One ITAM users only need to get an IAM refresh token and any user account that has access to Flexera One ITAM should be able to the same account to generate a refresh token.

Flexera IAM integration is based on refresh and access tokens where the access token is short-lived to keep Flexera One access secure and robust.

Note: This will also remove the need for a separate web service account as an interactive account with access to ITAM can be used to generate token to access SOAP APIs.

What About Existing Integration

Flexera One ITAM SOAP APIs existing integration using AGW token will keep on working, also includes Flexera App Broker / Admin Studio On-Prem integration with Flexera One ITAM. If you are accessing Flexera One ITAM SOAP APIs, we highly recommend transitioning existing Flexera One ITAM SOAP API integrations to Flexera One IAM as Flexera AGW would not support this integration later in Q4 2022.

App Broker 2022 R1 On-Prem release will have out-of-the-box integration support with Flexera One ITAM using Flexera IAM for our Flexera One ITAM customers still using App Broker On-Prem. Flexera recommends upgrading App Broker to 2022 R1 or later. For any support, Flexera recommends reaching out to the Flexera support team always there to help you.

What Do I Need to do?

Download the Flexera One ITAM SOAP API’s integration webAPI configuration file that contains the Organization ID you want to integrate to access data through SOAP APIs.Generate a new refresh to generate a short-lived access token using the Flexera One IAM user account that has access to Flexera One ITAM. Flexera IAM refresh token is used issue access token to access SOAP APIs.

Existing API endpoints

https://flexnetmanager.com/ManageSoftServices/ComplianceAPIService/ComplianceAPIService.asmx
https://flexnetmanager.eu/ManageSoftServices/ComplianceAPIService/ComplianceAPIService.asmx

New Endpoints for API Transition to Flexera One IAM

Flexera One ITAM Hosted in North America 
https://slo.app.flexera.com/ManageSoftServices/ComplianceAPIService/ComplianceAPIService.asmx?orgid=<insertorgid>

Flexera One ITAM Hosted in Europe
https://slo.app.flexera.eu/ManageSoftServices/ComplianceAPIService/ComplianceAPIService.asmx?orgid=<insertorgid>

Note: For UAT endpoints equivalent URL’s are available for North America(slo-uat.app.flexera.com) and Europe (slo-uat.app.flexera.eu) region.

Applies to

Flexera One ITAM

(4) Comments
tjohnson1
By Technical Writer
Technical Writer

@AamerSharif, with the AGW integration being deprecated in Q4 will there be an option to use the Flexera One API with a service account prior to that so that if a user leaves a new token does not need to be generated to use the API?

Many customers wish to use a service account vs an actual user account for their automation. 

AamerSharif
By Level 9 Flexeran
Level 9 Flexeran

Hi Tim,

Customer/s can use the same account but that account needs to be added to Flexera IAM (New SSO Technology built for Flexera One) and a new token need to be generated as it is a new identity provider and required a new token for security reasons.

Thanks

Aamer

longdinh
By
Level 5

Hi @AamerSharif,

I can see that you are mentioning only for endpoints for API Transition to Flexera One IAM in North America + Europe. Do we have the endpoint for APAC region?

I believe it is, if I am not wrong?

https://slo.app.flexera.au/ManageSoftServices/ComplianceAPIService/ComplianceAPIService.asmx?orgid=<insertorgid>

 

Thank you

ChrisG
By Community Manager Community Manager
Community Manager

@longdinh - yes, that looks like the URL to use for APAC. The URL root is listed on the following page: Safelist URLs and Endpoints