[BUG] Device ID not Matched

[bytesaber]

Checks

• I have read the FAQ section, searched the open issues, and still think this is a new bug.

Describe the bug you encountered:

I am attempting to get keepass2android approved for use at work. I use an android phone with a work profile. Keepass2Android works great to access OneDrive for my personal profile. However, there appears to be a bug with the work profile (a separate Google Play Store installation of keepass2android). There is an authentication ID not being passed, according to my security support team. I have included an image that they sent, to help describe what they need to happen. Currently I am able to get this working on the work profile, by means of a temporary bypass in our policy. Once they remove the temporary bypass, keepass2android no longer has access to our work provided OneDrive.

Describe what you expected to happen:

For the Device Identification to be passed back, and match, during authentication. This would allow my security team to avoid making an exception in our security policy.

What version of Keepass2Android are you using?

1.14r4

Which version of Android are you on?

16

[PhilippC]

Unfortunately it is not clear to me what this device identification is. I have followed standard procedures to do the authentication (https://github.com/PhilippC/keepass2android/blob/master/src/Kp2aBusinessLogic/Io/OneDrive2FileStorage.cs#L1011C1-L1013C29). Is there any official documentation about how this should be done in a OneDrive client application?