Authentication fails

Describe the bug

Unable to authenticate with the API.

Expected behavior

sdk.interactive.login_secret(client_id="automation@12345678.iam.panserviceaccount.com", client_secret="12345678-1234-1234-1234-123456789012", tsg_id=12345678)

Current behavior

unable to authenticate

sdk.interactive.login_secret(client_id="automation@12345678.iam.panserviceaccount.com", client_secret="12345678-1234-1234-1234-123456789012", tsg_id=12345678)
Profile retrieval failed.
Profile retrieval failed.

Possible solution

There was a recent change to the scoped permissions, whereas before we would pass scope in our API call as k/v pair scope: tsg_id:12345678 and now it's scope: profile tsg_id:12345678 email

Steps to reproduce

Try to authenticate in the same fashion as detailed in the documentation

1. sdk.interactive.login_secret(client_id="automation@12345678.iam.panserviceaccount.com", client_secret="12345678-1234-1234-1234-123456789012", tsg_id=12345678)

Screenshots

Context

unable to authenticate prevents the use of the SDK.

Your Environment

• Version used: unable to find version, installed via pip install 'prisma-sase-sdk-python @ https://github.com/PaloAltoNetworks/prisma-sase-sdk-python'

• Environment name and version (e.g. Chrome 59, node.js 5.4, python 3.7.3): python3.10

• Operating System and version (desktop or mobile): Windows WSL2 (Ubuntu 20.04)

• Link to your project: n/a

Start at the SDK's interactive.login_secret entry point and trace how the authentication scope and profile retrieval request are built. Reproduce the documented call in Python 3.10, then verify that authentication completes and profile retrieval no longer fails with the required scoped permissions.