-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support 0x0000000D ulType in PAC_INFO_BUFFER #11
Comments
Hello, @krasnovu. May I ask you to attach some test vector of PAC with claims if you have one? |
Yes, of course! |
Oops, sorry, it looks like there is a buffer, but its length is 0. My mistake, it turns out to be a false issue, because I don't have another PAC yet. :-( |
@krasnovu anyway i've added support for remaining claims (some work is pending on decoding credentials, but other things should work) |
@krasnovu credentials decoding is also done. |
Thank you, @oiweiwei ! Once I get a chance to check it out, I'll be sure to leave a feedback . |
Greetings, @oiweiwei! I've got a PAC that can't unmarshal. I don't know if I should create a new ishyu or here? I'll put it here. |
i've added pac-decoder tool in helpers dir:
both samples work for me. |
@krasnovu perhaps you are trying to use some string encoding (or encrypted bytes) as an input the pac.Unmarshal in your code instead of raw data you've provided here. |
Closing the issue as requested support has been added. |
Greetings, @oiweiwei !
I found that the
0x0000000D (13) Client claims information PAC_CLIENT_CLAIMS_INFO
type is not supported.Could you please add support for this in PAC?
The text was updated successfully, but these errors were encountered: