Configuration reload leads to tidc error on IDPs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Moonshot Trust-Router |
Fix Committed
|
High
|
Jennifer Richards |
Bug Description
When configuration is reloaded by a file change on the TR server, all the IDPs begin to be unable to contact the TR server due to Acceptor Identity different than expected.
Steps to reproduce:
1) Have a working TR infrastructure.
2) Launch a successful "tidc" query from an IDP (or even the TR)
3) Modify (or just touch!) the configuration file. The TR server detects the change and reloads configuration.
4) Try again with the "tidc" command and get the following:
Moonshot TID Client 3.0.2
TIDC Client:
Server = assent-tr.lxd, rp_realm = assent-tr.lxd, target_realm = assent.lxd, community = assent.lxd, port = 12309
Warning: dh_check failed with 8
: the g value is not a generator
tidc_open_
gss_connect: Connecting to host 'assent-tr.lxd' on port 12309
Error returned by gss_init_
major error <1> Invalid token was supplied
minor error <1> Acceptor identity different than expected
AuthenticateToS
Error in tidc_open_
5) on the TR side you get this:
Configuration updated successfully.
ReadBuffer failed: Connection reset by peer (err = 104)
ReadToken failed: Connection reset by peer (err = 104)
Authenticate failed: Connection reset by peer (err = 104)
tids_handle_
affects: | moonshot → moonshot.tr |
affects: | moonshot.tr → moonshot-tr |
Changed in moonshot-tr: | |
status: | New → Fix Committed |
assignee: | nobody → Jennifer Richards (jennifer-k) |
importance: | Undecided → High |
I forgot to mention that restarting the TR server fix the issue.