Answer
Treat any deprecation notice for an authentication method as a scheduled cutover, not an optional upgrade — confirm the supported replacement (typically a token-based flow) for your release and start migrating before the old method is actually removed. See authenticate and get access for the token-based pattern.