Fix export and detail API inconsistencies for remote auth config #2198
+35
−24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The export and detail APIs had several inconsistencies that were blocking UI development:
use_pkceattribute in export endpoint responsesSolution
UsePKCEfield toRemoteAuthConfigstruct with proper JSON tagsuse_pkce,client_id, etc.)UsePKCEfieldTesting
use_pkcefield for both true valuesImpact
use_pkcefield for workload duplicationfixes #2188