Ildar Abdullin

I think the main problem here is that launchd daemons(and Authorization plugin in particular) are not able to use data protection keychain APIs and therefore we see entitlement level error...

@kochste77 , device token and device fingerprint were omitted on purpose in public API. You are not allowed to use these params in iOS applications Documentation links: https://developer.okta.com/docs/reference/api/authn/#primary-authentication-with-trusted-application https://developer.okta.com/docs/reference/api/authn/#primary-authentication-with-device-fingerprinting

> @IldarAbdullin-okta I've just looked at #120. You said that `deviceToken` is omitted on purpose 😯 > As I can see at [Device Token Best Practices](https://developer.okta.com/docs/reference/api/authn/#device-token-best-practices) - native apps can...

Hi @efeluke , Thank you for creating this ticket. I will add required functionality early next week. I will keep you posted! Ildar

HI @efeluke, According to the documentation: `Specifying your own deviceToken is a highly privileged operation limited to trusted web applications and requires making authentication requests with a valid API token....

Mobile applications are untrusted because they can't use admin API token due to security reasons Regarding Android SDK, it is built on top of [java SDK](https://github.com/okta/okta-sdk-java), and java SDK is...

Hi @eberttc , I'm going to re-open this ticket and bring this to the team for discussion. There could be a chance that server just ignores deviceToken if api token...

Thanks a lot for the contribution, @Dozer1170 ! Could you please create github issue so I can prioritize it? Your fix looks good, however I would like to expose this...