Set the creatorUid to ANDROID-CloudTAK-${user.email} when creating missions

[brian7704]

Changes the creatorUid when creating missions to match the UID used elsewhere in CloudTAK. This solves an error I was getting while updating OpenTAKServer to work with CloudTAK.

[ingalls]

@brian7704 This is great, quick Q - Is the expectation that UID is just consistent but nothing is locked to the format of the value itself?

Context is that the ANDROID- prefix was something I thought was required 2 years ago when I started reverse engineering some of this stuff and I now realize isn't. It probably should just got dropped in favour of a pure uuid or CLOUDTAK-<uuid>

Thoughts?

[ingalls]

In the near future I also need to checkout the ramifications of

TKS-871 validate client uid to prevent spoofing

In the recent 5.3 release

[brian7704]

@brian7704 This is great, quick Q - Is the expectation that UID is just consistent but nothing is locked to the format of the value itself?

Context is that the ANDROID- prefix was something I thought was required 2 years ago when I started reverse engineering some of this stuff and I now realize isn't. It probably should just got dropped in favour of a pure uuid or CLOUDTAK-<uuid>

Thoughts?

I believe that's correct. It's just expected to be unique and consistent but to my knowledge there's no format that it needs to adhere to. I know that iTAK uses just a UUID and WinTAK uses a format like this S-1-5-21-3880475707-799676908-474682855-1001