Serverless Stack

<@U01NDPM3NDT> Yup, here’s an example. You can find both `Domain` and `Client ID` inside application settings in your Auth0 dashboard.
```new Auth(this, "Auth", {
  auth0: {
    domain: "<https://myorg.us.auth0.com>",
    clientId: "UsGRQJJz5sDfPQDs6bhQ9Oc3hNISuVif",
  },
});```
Full doc here - <https://docs.serverless-stack.com/constructs/Auth#allowing-users-to-login-using-auth0>

Oh btw, here’s an example on using Auth0 with Api construct - <https://serverless-stack.com/examples/how-to-add-auth0-authentication-to-a-serverless-api.html>

thanks! I did all that today and worked great! :100:

the only issue I had was similar to the one we had to other day related to an incorrect package being used

not sure if there could be a way to pin dependencies in a better way to avoid those errors

i had to add `"@aws-cdk/aws-iam": "1.89.0"`   , without that it was pulling `PolicyStatement`  from somewhere else, which ended up making attachPermissionsToRole fail due to invalid instance type (`PolicyStatement2 != PolicyStatement`).

Oh yeah, this `PolicyStatement` issue is fixed in this release also.

it was around here: <https://github.com/serverless-stack/serverless-stack/blob/master/packages/resources/src/util/permission.ts#L58>

I’m going to push out a fix for the `lambda.Runtime` conflict u ran into last time

But yeah, let me know if you run into more issues like this :grin:

sure, it happened to another friend the other day .. <@U01PG3AMRMW> do you remember where was it?

the quickest fix is actually removing the `node_modules` folder and  `package-json.lock` or `yarn.lock`  file

and then do a clean install with `npm install`  or `yarn`

This problem usually happens after updating SST/CDK version.

The spot of code is here <https://github.com/serverless-stack/serverless-stack/blob/master/packages/resources/src/Function.ts#L112>

<@U01JVDKASAC> i shared your Auth0 example doc with our Auth0 Contact person, so he can share it with other clients in the future, and maybe get the word out about SST .. It was a nice addition for SST

Thanks <@U01NDPM3NDT>! Really appreciate the support :grin: