-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Labels
Priority-MediumMedium-priority tasks that are important but not urgent.Medium-priority tasks that are important but not urgent.bugIssues or problems that need to be fixed.Issues or problems that need to be fixed.
Milestone
Description
Name and Version
0.14.1
What steps will reproduce the bug?
1.Open an Entity Toolset (e.g. GitHub).
2.Set Authentication method to OAuth.
3.Set PKCE method = None.
4.Click Log In.
5.Login is successful.
6.Open an Asset Toolset (same provider, e.g. GitHub).
7.Set Authentication method to OAuth.
8.Set PKCE method = None.
9.Click Log In.
What is the expected behavior?
Asset Toolsets should behave the same as Entity Toolsets.
When PKCE = None, codeChallengeMethod should be handled consistently, allowing successful login.
What do you see instead?
Login fails for Asset Toolset.
Unlike Entity Toolsets, the value is not populated correctly for Core, which results in an OAuth error.
Additional information
Same OAuth provider (GitHub).
Same PKCE configuration.
Works for Entity Toolsets, fails only for Asset Toolsets → likely a backend/Core integration inconsistency.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Priority-MediumMedium-priority tasks that are important but not urgent.Medium-priority tasks that are important but not urgent.bugIssues or problems that need to be fixed.Issues or problems that need to be fixed.
Type
Projects
Status
To-Do