fix(19.7): RB-WR-02 a padded token scope name fails boot
validatePluginTokenScope checked the trimmed name with pact.ValidTokenScopeName while compileTokenScopes registered the untrimmed one, so " blog:read" booted, was listed under its padded name and could never be granted, and the duplicate check depended on registration order. The name is now validated exactly as registered, which is the shared rule pact.ValidTokenScopeName states.
This commit is contained in:
@@ -9,7 +9,8 @@ import (
|
||||
// TestTokenScopeNameParity pins plan 07's shared scope name rule (P-30):
|
||||
// cabana's plugin scope validation accepts and refuses exactly the names
|
||||
// pact.ValidTokenScopeName does (the table of pact's TestFrontendTokenScopes;
|
||||
// "*" is refused by both, by cabana also as reserved).
|
||||
// "*" is refused by both, by cabana also as reserved). A padded name is
|
||||
// refused by both: cabana validates the name it registers, untrimmed.
|
||||
func TestTokenScopeNameParity(t *testing.T) {
|
||||
names := []struct {
|
||||
name string
|
||||
@@ -25,6 +26,11 @@ func TestTokenScopeNameParity(t *testing.T) {
|
||||
{"a:b:c", false},
|
||||
{"*", false},
|
||||
{"with space", false},
|
||||
// RB-WR-02: a padded name is refused as registered, not trimmed first.
|
||||
{" read", false},
|
||||
{"read ", false},
|
||||
{"read\n", false},
|
||||
{"\tblog:read", false},
|
||||
}
|
||||
for _, c := range names {
|
||||
if got := pact.ValidTokenScopeName(c.name); got != c.ok {
|
||||
|
||||
Reference in New Issue
Block a user