@Edent While Apple dropped their prefix from the otpauth scheme, their approach is not “identical to Google’s.”
Apple:
issuer label prefix: “the proper name of your service”
issuer parameter: use a domain as “[Apple Passwords] uses this field to suggest credentials when setting up a new code generator”
Google:
“if both the issuer parameter and issuer label prefix are present, they should be equal”
(They conflict but my own tests show it is more pragmatic to follow Apple’s recommendations.)
@Edent references:
https://developer.apple.com/videos/play/wwdc2024/10125/?time=751 (Apple, WWDC 2024)
https://developer.apple.com/documentation/authenticationservices/securing-logins-with-icloud-keychain-verification-codes (Apple, 2021)
https://github.com/google/google-authenticator/wiki/Key-Uri-Format (Google, 2018)
@andrewe catch me up. What specifically are you referring to?
@Edent Your useful primer on the otpauth URI scheme and the lack of a formal specification: https://shkspr.mobi/blog/2022/05/why-is-there-no-formal-specification-for-otpauth-urls/
@andrewe Ahh! I see. That was written a few years ago. I've no idea what's changed in the meantime.