feat(authentication): Add Authenticator config options for session store and session cookie name.

[helpisdev]

Description

As documented in the InMemorySessions source (emphasis mine):

InMemorySessions implements the [Sessions] interface by storing the sessions in-memory. This is obviously not suitable for production and only meant for testing purposes.

the default implementation for the session sotre is not suitable for production, thus an alternative session store implementation must be used by the end user. Currently there isn't any option to bring your own session store, so I added this option. I also added an option to change the default cookie name for completeness sake.

I don't know how you run your testing suite so I haven't added any tests yet.

Definition of Ready

• [x] I am happy with the code
• [x] Short description of the feature/issue is added in the pr description
• [ ] PR is linked to the corresponding user story
• [ ] Acceptance criteria are met
• [ ] All open todos and follow ups are defined in a new ticket and justified
• [ ] Deviations from the acceptance criteria and design are agreed with the PO and documented.
• [x] No debug or dead code
• [x] My code has no repetitions
• [ ] Critical parts are tested automatically
• [ ] Where possible E2E tests are implemented
• [ ] Documentation/examples are up-to-date
• [ ] All non-functional requirements are met
• [ ] Functionality of the acceptance criteria is checked manually on the dev system.

[livio-a]

@helpisdev thanks for this addition. This definitely makes sense.

If you like to get a gift from us, please write an email to hi@zitadel.com

[github-actions[bot]]

:tada: This PR is included in version 2.3.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: