Get The Head Right

Hi folks,
I’ve been trying to test my SSIS solution and getting 403 errors. NHSE said the handshake is successful but there’s a problem with the authorisation header.
Having read back through the documentation, I thought I found the problem that the mailbox wasn’t upper-case but I’m still getting the error.
I’m definitely using a different nonce every time and I’m all out of ideas. Here’s one example of what I’m sending:

Accept application/vnd.mesh.v2+json
Address {https://msg.intspineservices.nhs.uk/messageexchange/RH8OT001/outbox}
AllowAutoRedirect TRUE
AllowReadStreamBuffering FALSE
AllowWriteStreamBuffering TRUE
AuthenticationLevel MutualAuthRequested
AutomaticDecompression None
CachePolicy {Level:BypassCache}
ClientCertificates {System.Security.Cryptography.X509Certificates.X509CertificateCollection}
Connection null
ConnectionGroupName null
ContentLength -1
ContentType application/octet-stream
ContinueDelegate null
ContinueTimeout 350
CookieContainer null
CreatorInstance {System.Net.WebRequest.DesignerWebRequestCreate}
Credentials null
Date {01/01/0001 00:00:00}
Expect null
HaveResponse FALSE
Headers {
Accept: application/vnd.mesh.v2+json
Content-Type: application/octet-stream
authorization: NHSMESH RH8OT001:1fcbfdd8-66d7-47ff-9bf7-b597c425c016:0:202611040912:5cc72b3a83c68ed50407f807e6b2dfb3ffd2960a655fd4ab1a4e4e10f141ec72
mex-clientversion: X26HC005
mex-osarchitecture: x64
mex-osdescription: Windows
mex-osversion: Microsoft Windows NT 10.0.26200.0
mex-workflowid: DPS_EPMA_SUBMISSION
mex-filename: 2611020745RH8wc1026_Admin.xml.gz
mex-localid: 2611020745RH8wc1026
mex-from: RH8OT001
mex-to: X26HC005
content-encoding: gzip
mex-content-checksum: 5cc72b3a83c68ed50407f807e6b2dfb3ffd2960a655fd4ab1a4e4e10f141ec72
}
Host msg.intspineservices.nhs.uk
IfModifiedSince {01/01/0001 00:00:00}
ImpersonationLevel Delegation
KeepAlive TRUE
MaximumAutomaticRedirections 50
MaximumResponseHeadersLength 64
MediaType null
Method POST
Pipelined TRUE
PreAuthenticate FALSE
ProtocolVersion {1.1}
Proxy {System.Net.WebRequest.WebProxyWrapper}
ReadWriteTimeout 300000
Referer null
RequestUri {https://msg.intspineservices.nhs.uk/messageexchange/RH8OT001/outbox}
SendChunked FALSE
ServerCertificateValidationCallback null
ServicePoint {System.Net.ServicePoint}
SupportsCookieContainer TRUE
Timeout 100000
TransferEncoding null
UnsafeAuthenticatedConnectionSharing FALSE
UseDefaultCredentials FALSE
UserAgent null

Hi Cory,

Your previous successful connection attempts to RH8OT001 have all been in the Path to Live DEP environment.
This failed attempt is in the INT environment.

Please can you check that you are using the password for RH8OT001 in the INT environment that the ITOC Support Desk provided.

If you’re not sure, please get in touch with them and ask that they reset it for you.

Kind Regards
Paddy

Hi Paddy,
I’m pretty certain I’ve only ever used:
https://msg.intspineservices.nhs.uk

I’ve just found some more documentation (https://digital.nhs.uk/services/path-to-live-environments/deployment-environment not linked anywhere from the MESH API development page) that says the DEP environment is:
https://msg.dep.spine2.ncrs.nhs.uk

I’m certain I’ve never used that URL.
The only other URL I have in my script is the live one, but this shouldn’t be used because my script chooses the URL based on the package parameter, which has always been “PtL” not “Live”:
https://mesh-sync.spineservices.nhs.uk

Are any of the URLs mentioned above the correct one for my use case? The “mesh-sync” one I believe is for User Acceptance Testing, which I shouldn’t be using yet because I haven’t completed the digital onboarding.
As directed in the documentation, I requested a mailbox for the Path to Live Integration Environment, so did something get mixed-up, there?

Best regards,
Cory