Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs: Add documentation for hosting Kratos on a sub domain #2774

Open
Tracked by #2792
JoblersTune opened this issue Jun 13, 2024 · 6 comments
Open
Tracked by #2792

Docs: Add documentation for hosting Kratos on a sub domain #2774

JoblersTune opened this issue Jun 13, 2024 · 6 comments
Assignees
Labels
pkg: documentation Changes in the documentation package. pkg: frontend Changes in the frontend package. user-doc-priority: low User doc priority is low user-docs

Comments

@JoblersTune
Copy link
Collaborator

JoblersTune commented Jun 13, 2024

There are specific configurations considerations and requirements when hosting Kratos on a subdomain. Need to figure out all these details and document them to make this flow easier for anyone attempting this in the future.

Might be related to #2949

@JoblersTune JoblersTune added type: localenv Local playground pkg: documentation Changes in the documentation package. labels Jun 13, 2024
@JoblersTune
Copy link
Collaborator Author

Some initial considerations:

Within the Kratos configuration file it might be necessary to set the domain property on cookies and sessions for session handling and CSRF cookies.

@JoblersTune JoblersTune added pkg: frontend Changes in the frontend package. and removed type: localenv Local playground labels Jul 2, 2024
@melissahenderson melissahenderson changed the title Add documentation for hosting Kratos on a sub domain Docs: Add documentation for hosting Kratos on a sub domain Sep 5, 2024
@mkurapov
Copy link
Contributor

@JoblersTune do you think we should provide an ory kratos config file in the docs for this?

@JoblersTune
Copy link
Collaborator Author

Ideally yes. But this kind of got bumped down the priority list since @tadejgolobic moved away from that approach so we haven't researched extensively or resolved the issue yet,. I.e more work than just docs still.

I think a line in the docs saying "if you host it on a sub domain read kratos docs" is sufficient for now unless it becomes a bigger priority.

@mkurapov
Copy link
Contributor

if you host it on a sub domain read kratos docs" is sufficient for now unless it becomes a bigger priority.

Makes sense, in the meantime, should we just provide a config file similar to testnet's current deployment to show a working solution? We don't need to mention sub domains.

@brad-dow
Copy link
Contributor

@JoblersTune @mkurapov
Currently, our docs contain this brief aside and a link to the Kratos docs. Should I put this issue back in the user docs backlog or are we at a point where we can build onto this?

Image

@JoblersTune
Copy link
Collaborator Author

I think that's up to the Rafiki team. It was a priority when we were using it that way ourselves for Rafiki Money but we pivoted approaches. Personally I wouldn't make this a priority unless someone asked about it. But I also don't think it's my call any more.

@mkurapov perhaps you can provide an answer for @brad-dow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pkg: documentation Changes in the documentation package. pkg: frontend Changes in the frontend package. user-doc-priority: low User doc priority is low user-docs
Projects
Status: Todo
Status: Backlog
Development

No branches or pull requests

4 participants