You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When configuring servers, too many times the value {keyId} is used instead of {keyID} (and/or the other way around). This causes either the services to fail or run with a bad URL endpoint.
A Bit of History
Initially keyId use to be present in commit 289f54f, but along with keyID in the same file.
Later keyID in commit 5260d89 is consistently used in both examples.
Problem
When configuring servers, too many times the value
{keyId}
is used instead of{keyID}
(and/or the other way around). This causes either the services to fail or run with a bad URL endpoint.A Bit of History
Initially
keyId
use to be present in commit 289f54f, but along withkeyID
in the same file.Later
keyID
in commit 5260d89 is consistently used in both examples.Comparison Example 1
clortho/resolver.go
Lines 28 to 31 in 289f54f
clortho/resolver.go
Lines 30 to 33 in 5260d89
Comparison Example 2
clortho/resolver.go
Lines 88 to 91 in 289f54f
clortho/resolver.go
Lines 199 to 202 in 5260d89
Suggested Solution
Make this
keyID
value case insensitive.The text was updated successfully, but these errors were encountered: