fix Vk provider tokens causing issues with database providers

[theneuetimes]

NOTE:

• It's a good idea to open an issue first to discuss potential changes.
• Please make sure that you are NOT opening a PR to fix a potential security vulnerability. Instead, please follow the Security guidelines to disclose the issue to us confidentially.

☕️ Reasoning

Currently the Vk provider returns extra unnecessary data along with the tokens (more exactly vk's internal user_id and email) which renders it unusable in some cases because the data can't be stored in a database (due to the previously mentioned properties missing in the schema).

This change makes sure only the required access_token and expires_at properties are returned.

🧢 Checklist

• Documentation
• Tests
• Ready to be merged

🎫 Affected issues

Please scout and link issues that might be solved by this PR.

Fixes: #3709

📌 Resources

• Security guidelines
• Contributing guidelines
• Code of conduct
• Contributing to Open Source

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
auth-docs	❌ Failed (Inspect)			Mar 26, 2023 at 2:09PM (UTC)
auth-docs-nextra	❌ Failed (Inspect)			Mar 26, 2023 at 2:09PM (UTC)

1 Ignored Deployment

Name	Status	Preview	Comments	Updated
next-auth-docs	⬜️ Ignored (Inspect)			Mar 26, 2023 at 2:09PM (UTC)

[balazsorban44]

Thanks, but the solution to this is not to restrict what the provider returns, but what the database accepts, by either extending the schema or overriding the adapter to ignore these fields.