sdk-nodejs | sdk-nodejs | Runtime Evironment library

PreSignUp_SignUp: Your standard Cognito pool (username/password) signup

PreSignUp_AdminCreateUser: When a user is created using the admin method (to be clear, not when your creating an admin, but when you are an admin creating a different user).

PreSignUp_ExternalProvider: If you have third party signup, like Google or facebook

yes you can't able to subscribe dynamic topic you have to change the policy "arn:aws:iot:ap-south-1:453533943651:topic/${iot:Connection.Thing.ThingName}/*" to *..for allow all device.then you can subscribe.topic/${iot:Connection.Thing.ThingName} this denotes the thingname should be come end of the topic. change to allow all you will able to subscribe.

I think this is because your function finishes before you get any results. One way to overcome this is using pattern for Async handlers shown in aws docs:

Docker layer caching is not supported in azure devops currently. The reason is stated as below:

In the current design of Microsoft-hosted agents, every job is dispatched to a newly provisioned virtual machine. These virtual machines are cleaned up after the job reaches completion, not persisted and thus not reusable for subsequent jobs. The ephemeral nature of virtual machines prevents the reuse of cached Docker layers.

1,However, Docker layer caching is possible using self-hosted agents. You can try creating your on-premise agents to run your build pipeline.

You may need to disable the Job's option 'Allow scripts to access the OAuth token'. For $(System.AccessToken) is passed to docker build using a --build-arg ACCESS_TOKEN=$(System.AccessToken), and its value varies for every run, which will invalid the caching.

2,You can also you use Cache task and docker save/load commonds to upload the saved docker layer to azure devops server and restore it on the future run. Check this thread for more information.

3,Another workaround as described in this blog is to use --cache-from and --target in your dockerfile.

If above workaround is not satisfying. You can submit a feature request to Microsoft Develop Team. Click Suggest a Feature and choose Azure Devops.

AWS SDK calls return an AWS.Request object, not the response to the actual API call, which typically arrives asynchronously.

You need to add a callback handler like so:

As stated in the Azure DevOps documentation:

Note: Azure Pipelines doesn't support all features of YAML, such as anchors, complex keys, and sets.

This means that you need to do away with all anchors (and aliases) in your YAML file. Moreover, you cannot expect a CircleCI configuration to be a valid Azure DevOps configuration. They are different tools and have a different configuration structure.

You should start by reading the Azure DevOps docs and then rewrite your file accordingly. This is not a trivial modification of the file.

The way you are trying to do is wrong

generation of private key and certificate is a multi-step procedure

When you try to create a keypair(private key & certificate) root-ca or intermediate-ca has to sign it then only it will be valid, this is called signing by using the concept of PKI

Fabric supports x509 certificate & ecdsa private key, you can generate root-ca certificate and sign certs outside.

Coming to your question about security of user credentials: you can always use fabric-ca to generate the sign certs and you have three options

• store in the server as file-storage
• store it in couchdb as key-value store
• store it in hardware using hsm or so

Check the issue here: =)

https://github.com/okta/okta-sdk-nodejs/issues/86

Issue definitely in the sdk itself, not in the script you are running.

Looks like issue is here https://github.com/okta/okta-sdk-nodejs/blob/master/src/memory-store.js#L22

Next workaround:

If you don't want to use the App ID login widget, and instead collect the credentials yourself and use the ROP REST API from a cloud function. You can do something like this: