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.

Sign up for GitHub

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

Jump to bottom

Look into incompatibilities between the cookie identity resolver and cookie service override #75

Open
ollieread opened this issue Dec 4, 2024 · 1 comment
Open

Look into incompatibilities between the cookie identity resolver and cookie service override #75

ollieread opened this issue Dec 4, 2024 · 1 comment
Assignees
@ollieread
Labels
status: planning The issue is being planned for the future type: fix Fix for a bug or other issue type: refactor Refactoring of code

Comments

@ollieread
Copy link
Member

There are potential incompatibilities between the cookie identity resolver and the cookie service override. I suspect that forcing the tenant cookie to exist outside the tenant-aware cookies is the best way to do this.
@ollieread ollieread self-assigned this Dec 4, 2024
@ollieread ollieread converted this from a draft issue Dec 4, 2024
@ollieread ollieread added type: fix Fix for a bug or other issue type: refactor Refactoring of code status: need info The issue requires more information labels Dec 4, 2024
@ollieread ollieread added this to the V1 Release milestone Dec 4, 2024
@ollieread ollieread moved this from Backlog to Ready in Sprout Development Dec 16, 2024
ollieread added a commit that referenced this issue Jan 9, 2025
@ollieread
chore: Throw a compatibility exception when using the cookie identity…
0c6e76f 
… resolver and service override

Refs: #75
@ollieread ollieread added status: planning The issue is being planned for the future and removed status: need info The issue requires more information labels Jan 9, 2025
@ollieread ollieread removed this from the V1 Release milestone Jan 9, 2025
@ollieread
Copy link
Member Author

For now, I'm throwing a compatibility exception, so I've moved this to low priority and removed it from the v1 milestone.

@ollieread ollieread closed this as not planned Won't fix, can't repro, duplicate, stale Jan 9, 2025
@github-project-automation github-project-automation bot moved this from Ready to Done in Sprout Development Jan 9, 2025
@ollieread ollieread reopened this Jan 9, 2025
@ollieread ollieread moved this from Done to In progress in Sprout Development Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ollieread ollieread

Labels
status: planning The issue is being planned for the future type: fix Fix for a bug or other issue type: refactor Refactoring of code
Projects
Sprout Development
Status: In progress
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ollieread