Default AAA server currently ignored
Bug #1643681 reported by
Jennifer Richards
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Moonshot Trust-Router |
Fix Committed
|
Low
|
Jennifer Richards | ||
Bug Description
I believe a change in behavio(u)r was introduced along with the initial implementaiton of the Dynamic Trust Router protocol. In the past, a request for an IdP realm without a configured AAA server would be sent to the configured default AAA server. Currently, this will result in an error being returned.
To fix this, the old behavio(u)r should be restored.
I'm not certain that the new behavio(u)r is described accurately here, need to verify this as well.
| description: | updated |
| description: | updated |
| Changed in moonshot-tr: | |
| status: | New → Triaged |
Revision history for this message
| Stefan Paetow (stefan-paetow) wrote | #1 |
| Changed in moonshot-tr: | |
| status: | Triaged → Fix Committed |
To post a comment you must log in.
I have just realised that we used to split this out into a separate file called 'peering.cfg'. Given that this functionality existed in v1.0 (as static peering mechanism), yes, leave it in. If the 'default_servers' list does not exist (it's always been optional, yes?) then it just returns an auth error. :-)