Problem:
When a client is using the MCC API they may be in specific smart on fhir context, which requires a server other than the MCC default server. The current behavior has a fallback scheme that will default the server if one is not provide. This is ok for rapid development, but for QA and Production environments this not desirable behavior since may go to the wrong server or not have the required credentials.
Solution:
Implement two new properties mcc.request.header.require.token and mcc.request.header.require.server that when set to true will throw and error if these two headers are not present.
Problem: When a client is using the MCC API they may be in specific smart on fhir context, which requires a server other than the MCC default server. The current behavior has a fallback scheme that will default the server if one is not provide. This is ok for rapid development, but for QA and Production environments this not desirable behavior since may go to the wrong server or not have the required credentials.
Solution:
Implement two new properties mcc.request.header.require.token and mcc.request.header.require.server that when set to true will throw and error if these two headers are not present.