sdk-javascript | High level library including multi | Websocket library

According to their documentation, the content is actually passed as children to Markdown.

So you can do this:

I can see that you have not given Group.Create permission in your permission set. Give this permission to create a group.

For Application permission type, these all permissions are required:

• Group.Create
• Group.ReadWrite.All
• Directory.ReadWrite.All

And for Delegated user permission type:

• Group.ReadWrite.All
• Directory.ReadWrite.All
• Directory.AccessAsUser.All

Your code works perfectly. I only updated tenant,clientId,clientSecret and MY_ISSUER in your code. Here is the whole code I ran.

try this and see node index.js tcp://127.0.0.1:4004

The underlying error here is likely due to one of two issues. Prior to making the reviseExtension call, you’ll want to make sure your POST body for Extension supplies a relationship to an ExtensionPackage. That ExtensionPackage must exist and be available for use on the Property.

Ref: https://developer.adobelaunch.com/api/reference/1.0/extensions/create/

The aws-crypto client-side library is primarily aimed at encryption/decryption use cases. If I understand your use case, I think a regular salted password hash would be appropriate.

The bcrypt package is quite popular and has a good interface. Or there are solutions that don't require third-party packages, for example using the native Node.js crypto module.

You can not use Client credential flow to get access token for /me endpoint. You should use auth code flow(acquireTokenWithAuthorizationCode) instead. Then you can call /me for the signed-in user.

If you must use client credential flow, you should call /users/{id | userPrincipalName} for a specific user.

Besides, if you want to call Microsoft Graph API, the value of resource which you used to get access token should be https://graph.microsoft.com.

Your syntax is correct but I'm afraid this isn't supported by the API itself. While AAD resources support $expand, there are some serious limitations:

1. It is only supported in the Beta version. As for why it is limited to Beta, it's a safe bet that it is due to the next point.

2. You can not use both $expand and $select in the same query. In other words, not only would /me?$expand=manager($select=displayName) fail, so would /me?$select=id,displayName&$expand=manager($select=displayName) or /me?$select=id,displayName&$expand=manager.

Given the value of data this ends up returning and being restricted to the Beta version, $expand is effectively relegated to a handful of edge-case scenarios when it comes to DirectoryObject.

My recommendation would be to avoid expanding the Manager in favor of setting your page size to 20 and constructing a batch request for each page of data to pull the manager. This allows you to dramatically reduce the amount of data over the wire, keeps the number of outbound calls to just two per page, and can be done entirely in the v1.0 version.

For more information on how batch requests are constructed, please see Batching in the SDK documentation.

If I remember correctly, unpkg.com was never an officially supported CDN (it was certainly not documented anywhere).

If you want to remain on v1.7 provided by unpkg, you can use this URI: