authr | : key : a flexible and expressive approach to access-control | Authorization library

In SharedPref class read method; use a null check before decoding the data. Ex:

I finally got this working using RestSharp. Below is the code if anyone else is looking for the solution:

try this

Function failed on loading user code. Error message: Node.js module defined by file index.js is expected to export function named doBackup()

Your Cloud Function to execute name, according to the error message is doBackup but the function that you are calling in index.js is exportDatabase. Please make sure that these names are the same, for example change exportDatabase to doBackup or change function to execute to exportDatabase

You should link to the docs you're referring to, which I believe is ServiceStack's JWT Modifying the Payload docs. Although it's not clear which example in the Customer Forums you're referring to.

It's also not clear what the question is, I'm assuming it's this statement:

When calling /auth/credentials?userName=****&password=**** I do not see the new values.

Where exactly are you expecting these values? If you're authenticating by credentials you're not Authenticating by JWT so you will not have these additional properties populated on your User Session. If they're embedded in your JWT's body payload then as TimeZone is a AuthUserSession property, it should be populated if it was contained within the JWT payload:

You could use JSON.parse(result.slice(9))

But there's probably a better way.

From your build output, as you've observed, the cache is indeed invalidated and you build a new image with the new contents of your directory. However, from the comments, you then run this container with a volume /app:/srv/shiny-server which will map access to this directory inside the container in /srv/shiny-server to the host at /app. Note that this path is an absolute path, rather than a relative path, so the files are on the host at /app rather than in your build directory in ./app.

Depending on your use case, there are various solutions. First, in the compose file, you have access to relative paths, so if you are testing locally (the typical reason to mount a volume), then you often want to mount the volume with a relative path like ./app:/srv/shiny-server. The result is the container runs with the contents of this directory without needing to rebuild the image, which is often preferred for faster development cycles.

If you do not want the volume mount, e.g. if this is in production and there's no need to access the files from outside of the container, then removing the volume mount from the compose file is preferred.

And lastly, if you need to have external access to these files, but you want them to be updated by the contents of your image, then you typically want to save the contents of the volume somewhere safe and update the volume with an entrypoint script. In my docker-base repo, I do this with the save-volume and load-volume scripts, one to run during the image build, and the other for during the entrypoint when running the container.

Cognito APIs are divided into two types. Signed and unsigned. The API that you are using (signUp) is an unsigned API and therefore cannot be restricted by IAM policy.

Basically all the admin calls like adminsignup where you can sign someone up for your service can be restricted, but the call you are making is designed for when users are registering themselves for your service. Restricting that API in IAM would not be very useful.

You can see all the unsigned APIs here

you can use redux over here or you can use the localstorage, cookie, sessions any one of these browser storage to set the values and when your component gets rendered you can retrieve this data from browser and make your API call. Though this is not the best approach but if you don't know how to use redux then you can apply this.