Error message when I use in enable now the function “Import from SAP Cloud ALM”

[wolfgangboehm]

I used the blog (https://community.sap.com/t5/technology-blogs-by-sap/sap-cloud-alm-and-sap-enable-now-present-collab...) and the tutorial (https://enable-now.sap.com/ic/pub/ext/index.html?show=slide!SL_68C3EB1C2C7F3680) to connect Cloud ALM and Enable Now and it connect both systems.

But … I get an error message when I use in enable now the function “Import from SAP Cloud ALM”
The import is running and end with the status “incomplete” and the written message is …

                Does your SAP Cloud ALM tenant support solution documentation?
                forbidden to access the resource (403)

[john_p_grimes · Accepted solution]

This sounds identical to a problem users frequently face when using the SAP Cloud ALM APIs for the first time. The root cause is usually related to the SAP Cloud ALM API Service Instance not being assigned the necessary authorization scopes. It happens so frequently, we have a KBA on that topic: 3425859 - '403 Forbidden' when testing SAP Cloud ALM outbound APIs

Have you verified that the SAP Cloud ALM API Service Key you are using has the correct scopes in its Service Instance? The KBA above points to another document with instructions on how to find out what scopes are currently assigned to a Service Instance.

I checked the SAP EnableNow documentation and it mentions that at least the following scopes should be assigned to the Service Instance: 

• calm-api.documents.read
• calm-api.documents.write
• calm-api.processauthoring.delete
• calm-api.processauthoring.read
• calm-api.processauthoring.write
• calm-api.processmanagement.delete
• calm-api.processmanagement.read
• calm-api.processmanagement.write
• calm-api.projects.read
• calm-api.projects.write

[wolfgangboehm · Accepted solution]

Hello, we updated the SAP Cloud ALM API Service Key 

[wolfgangboehm · Accepted solution]

Hello, we updated the SAP Cloud ALM API Service Key one more time with this values:

"authorities": [
            "$XSMASTERAPPNAME.calm-api.analytics.providers.read",
            "$XSMASTERAPPNAME.calm-api.analytics.read",
            "$XSMASTERAPPNAME.calm-api.bm.read",
            "$XSMASTERAPPNAME.calm-api.bsm.read",
            "$XSMASTERAPPNAME.calm-api.bsm.write",
            "$XSMASTERAPPNAME.calm-api.csa.read",
            "$XSMASTERAPPNAME.calm-api.defects.read",
            "$XSMASTERAPPNAME.calm-api.demo-tasks.read",
            "$XSMASTERAPPNAME.calm-api.documents.read",
            "$XSMASTERAPPNAME.calm-api.documents.write",
            "$XSMASTERAPPNAME.calm-api.event-situations.write",            
            "$XSMASTERAPPNAME.calm-api.exm.personal.read",
            "$XSMASTERAPPNAME.calm-api.exm.read",
            "$XSMASTERAPPNAME.calm-api.exm.write",
            "$XSMASTERAPPNAME.calm-api.hm.read",
            "$XSMASTERAPPNAME.calm-api.hm.write",
            "$XSMASTERAPPNAME.calm-api.iep.read",            
            "$XSMASTERAPPNAME.calm-api.integration-monitoring.personal.read", 
            "$XSMASTERAPPNAME.calm-api.integration-monitoring.read",            
            "$XSMASTERAPPNAME.calm-api.integration-monitoring.write",
            "$XSMASTERAPPNAME.calm-api.jobs.read",
            "$XSMASTERAPPNAME.calm-api.landscape.read",
            "$XSMASTERAPPNAME.calm-api.logs.read",
            "$XSMASTERAPPNAME.calm-api.logs.write",
            "$XSMASTERAPPNAME.calm-api.metrics.read",
            "$XSMASTERAPPNAME.calm-api.metrics.write",
            "$XSMASTERAPPNAME.calm-api.processauthoring.delete",
            "$XSMASTERAPPNAME.calm-api.processauthoring.read",
            "$XSMASTERAPPNAME.calm-api.processauthoring.write",
            "$XSMASTERAPPNAME.calm-api.processmanagement.delete",
            "$XSMASTERAPPNAME.calm-api.processmanagement.read",
            "$XSMASTERAPPNAME.calm-api.processmanagement.write",
            "$XSMASTERAPPNAME.calm-api.projects.read",
            "$XSMASTERAPPNAME.calm-api.projects.write",
            "$XSMASTERAPPNAME.calm-api.requirements.read",
            "$XSMASTERAPPNAME.calm-api.rum.read",
            "$XSMASTERAPPNAME.calm-api.rum.write",
            "$XSMASTERAPPNAME.calm-api.sum.read",
            "$XSMASTERAPPNAME.calm-api.sum.write",
            "$XSMASTERAPPNAME.calm-api.tasks.read",
            "$XSMASTERAPPNAME.calm-api.tasks.write",
            "$XSMASTERAPPNAME.calm-api.tests.read",
            "$XSMASTERAPPNAME.calm-api.traces.read",
            "$XSMASTERAPPNAME.calm-api.traces.write"
        ]

and get still the same error.

[john_p_grimes · Accepted solution]

In that case you should have all the data necessary to use the SAP Cloud ALM API. Have you tried running requests against the SAP Cloud ALM API using a REST API client tool (e.g. cURL, Bruno, Postman, etc.) to see if it indicates any errors?

It sounds like the issue could be on the SAP EnableNow side. I suggest that you leave a comment on the blog you followed, the author should be able to clarify why EnableNow has that error message.

[wolfgangboehm · Accepted solution]

Hello, thanks for the support; 

with your last hint to test with an requests against the SAP Cloud ALM API we found the problem and could fix it.

best regards