CMS API : Fetching typeDefinitions / namespaces for regular users ?

@Med_2024 , in general, CMS has the option to apply acls.
I did a quick test where I used VS Code to define a namespace and type, then deployed this.
After that I created/added a new user (normal user with no specific roles) to my app (in the tenant/subscription).
In my Rest client I retrieved an access-token and did a GET on https://na-1-dev.api.opentext.com/cms/type-definitions/med24_med2024mydef which did return the type definition.

Requesting the type definition acl shows via https://na-1-dev.api.opentext.com/cms/type-definitions/med24_med2024mydef/aclshows the following permits for the type definition:
"permits": [
{
"identity": "subscription_users",
"identity_type": "role_alias",
"permissions": [
"browse"
]
}
],

Can you check the permits for your type definition? Does it also have the browse permission for subscription users?

Can you please try the following:

Go to Admin console, login as the Organization admin and then go to your Tenant → Apps → Your App → User Management → Roles → ims_user and add your user there.

Get a new token and then try to get the type again.

And if you add them to the ims_admin role, do they see it then?

Can you check the following:

On your initial application, get the subscription ID (In Admin center, Organization → Tenant → Apps → Click on your app) and see it in the browser address:

Check the ACL on the type you are not seeing with a normal user:

Get the ACL ID for the type: https://{{host}}/cms/type-definitions/{{type_name}}

In the result JSON, get the acl_id

Then get the ACL Information: https://{{host}}/cms/permissions/{{acl_id}}

In the result JSON, check the ACL name:

The ID inside the name of the ACL should match the subscription ID, otherwise the role_alias is not going to return your current user within the subscription.

You can manually add in the ACL new groups/users and they will then see the type definition.

@Med_2024 , you can follow the documentation on developer.opentext.com for the Content Metadata Service (https://developer.opentext.com/imservices/products/contentmetadataservice/apis/contentmetadata) in the section Permissions, PATCH Permission:

I used the following:

• I have a user that logs in to a different subscription, a type defined in the initial subscription, I log in and don't see the type (404 error on getting the type)
• The user is part of a Tenant Group (AllUsers_Google IDP)
• added a Tenant Group in the ACL definition for my initial subscription like this:
  • get a token with an admin account
  • get the type permission id (see my previous answer)
  • API patch to the /cms/permissions/{acl_id}
  • payload (in red is what I added, rest was already there - you can probably omit the description and initial permits since this is a patch call):

• ran the type get call again (same token) and it works

Hello @Med_2024 ,

If the group is created at the App Level, it will be a subscription_group.

You can add a specific user either by email or by their ID - to get their ID, see the Administration API: https://developer.opentext.com/imservices/developertools/developeradmin/apis/developeradministrationapi and look at the Tenant Users:

The calls above will return the user id.

PS: when adding a specific user, in the patch call, the permits element has the following structure:

• identity will be the email or ID of the user
• identity_type will be "user"
• permissions will be the array of permissions