@maciej-wisniowski That was done when we found that there was a bug in

#FROM fusionauth/fusionauth-app:1.19.4

and we replaced it with:

FROM fusionauth/fusionauth-app:1.19.7

@maciej-wisniowski said in Using custom parameters with login page:

[@helpers.hidden name="custom_parameter" /]

I did not know you could do that. Thanks for sharing your solution!

@dan I am using caprover as PaaS, and it has NGINX fully integrated. It's only happening on their latest version. I already raised an issue with them (https://github.com/caprover/caprover/issues/1035).

I tried to reconfigure their proxy manually but couldn't get it to work. I just rolled it back to their earlier version.

@zamman welcome to the FusionAuth community!

FusionAuth doesn't support JWEs at this time. If you wanted to encrypt some data in your JWT, you could use a JWT populate Lambda, as long as the encryption algorithm can be implemented in straight javascript embedded in the lambda (you cannot pull in third party libraries). This MIT licensed code might work; I haven't tested it though. That's not going to create a full fledged JWE, but may suit your needs.

We don't have JWE support on our near term roadmap (you can learn more about our roadmap here). If this is a feature you need to have in a set schedule and are willing to spend money to get, please feel free to contact us about our professional services.

Alternatively, please file a feature request in our github issues list with an explanation of the use case. We draw from these feature requests based on community support as indicated by upvotes.

@cameron-chapman,

Typically the best place to get answers for these kinds of questions is our contact form.

Here is a FAQ with some compliance information.

And here's another one, with slightly different but still useful information.

But if you have specific questions, please reach out directly.

@dan said in Systemd service template:

https://fusionauth.io/direct-download/

To Add to what @dan mentioned, you can install .deb or .rpm packages using the fast path install method. It will default to zip file installation.

For additional ways to call it - see the Fast Path install guide.
https://fusionauth.io/docs/v1/tech/installation-guide/fast-path/

@vexana

I think you want to add a claim into a token? Does this lambda help? https://fusionauth.io/docs/v1/tech/lambdas/jwt-populate/

Or can you be more precise in what you are looking to do?

This issue was resolved and released as part of 1.24.0.

More here: https://fusionauth.io/docs/v1/tech/release-notes/#version-1-24-0

@vexana succeeded, but had another question, so I forked the topic: https://fusionauth.io/community/forum/topic/811/mapping-fusionauth-roles-to-elasticsearch

Hiya @priyankakumari3058

I'm not sure you're posting in the right forum. This forum is for questions and discussion about FusionAuth, not kibana.

I think you might want the elasticsearch forums: https://discuss.elastic.co/

Hope that helps.

@dan Thanks it worked !

My first question is a) when I setup the dashboard on server A. Can I assume that all the servers (behind a load balancer) will get the same configuration?

You need to distribute the configuration file or the environment variables yourself. You could scp the configuration file to each server, for example.

b) I want to make sure that FA is using the RDS database and not a local one in each docker container. How can I prove to myself that FA is using the RDS?

I'm not sure how you installed this, but you could remove postgresql from the docker-compose file. You can also shut down the RDS instance and see if FusionAuth fails.

You can also look for a line in the startup log file that looks like this:

fusionauth_1 | 2021-02-02 9:23:53.070 PM INFO com.inversoft.jdbc.hikari.DataSourceProvider - Connecting to PostgreSQL database at [jdbc:postgresql://db:5432/fusionauth]

This line is connecting to a local postgresql database, but you should see the configuration value pointing to the RDS hostname in yours.

So I just finished writing up an SSO document (not yet published, in review) and SSO and refresh tokens are orthogonal. Refresh tokens are used when you have a client who wants to get a new JWT, and SSO is used to transparently log a user in when you are using the hosted login pages.

So I wouldn't worry about the refresh token appearing or disappearing.

... handling SSO in my application but looks like my SSO session is dropped after some short time ~1h, but Session timeout for the tenant is set to 10 days

What does the fusionauth.sso cookie have for the maxage/expires value?