FMS clients currently need to be explicitly configured to send the FMS id with each request, but we're changing that behaviour to be automatic. Consequently, FMS-endpoint should add external_id (or fms_id, see #19 ) as a required attribute in its service discovery responses.
Note that this only makes sense if we know the client to be an FMS installation that will provide the FMS ID (this is important, because if it's not, the attribute will appear as a (nonsensical) prompt to the user. So this may need an "is FMS?" config setting in the clients table.
See mysociety/fixmystreet#329 for the proposed change to FMS.
This would make FMS sending to FMS-endpoint clients happen automagically.
FMS clients currently need to be explicitly configured to send the FMS id with each request, but we're changing that behaviour to be automatic. Consequently, FMS-endpoint should add external_id (or fms_id, see #19 ) as a required attribute in its service discovery responses.
Note that this only makes sense if we know the client to be an FMS installation that will provide the FMS ID (this is important, because if it's not, the attribute will appear as a (nonsensical) prompt to the user. So this may need an "is FMS?" config setting in the clients table.
See mysociety/fixmystreet#329 for the proposed change to FMS.
This would make FMS sending to FMS-endpoint clients happen automagically.