question

aisecond-2443 avatar image
0 Votes"
aisecond-2443 asked aisecond-2443 commented

How should we parse BinarySecurityToken?

Our MDM server received an enrollment request from the client. We got BinarySecurityToken and tried to parse it, but it always went wrong. How do I resolve BinarySecurityToken?
We did it in the following way
certificateSigningRequestDer, err := base64.StdEncoding.DecodeString(binarySecurityToken)
if err != nil {
return nil, err
}
// Decode and verify CSR
csr, err := x509.ParseCertificateRequest(certificateSigningRequestDer)
if err != nil {
panic(err)
}

enrollment-protocol.txt has detailed data

Can you help us resolve this parsing error?`enter code here`




azure-information-protection
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @aisecond-2443,

I've retagged your question under secuity center for better visibility. Is the enrollment against clound tenant or on-prem?

0 Votes 0 ·

Thanks for your reply, it is clound tenant .We developed according to the documentation here


0 Votes 0 ·

We tried to parse BinarySecurityToken, and then responded to Windows10, but still encountered the previous error code..Can you help us to see if the BinarySecurityToken is processed incorrectly? Here is the detailed data


0 Votes 0 ·

0 Answers