What should be replaced with 'plus.me' scope on G Suite Marketplace?

Question

Until currently we have used plus.me (https://www.googleapis.com/auth/plus.me) scope for OpenID Connect on G Suite Marketplace.But 'plus.me' scope will discontinue with Google+ API shutdown.

Google Sign-in(And Google OpenID Connect) replace to 'openid' scope from 'plus.me'. My code has been already migrated but G Suite Marketplace is not accept 'openid' because it only accept URL format.

What should be replaced with 'plus.me' scope on G Suite Marketplace?

UPDATED: Even if neither 'openid' nor 'plus.me' is registered, I confirmed that OpenID Connect is work without OAuth confirmation screen.

If 'openid' scope is a specification that does not need to be registered on G Suite Marketplace SDK and this specification will be keep, I would like to get reference written by Google or hear from staff of Google.

Answer 1

Currently, the issue is fixed and 'openid' scope is be able to register.

Answer 2

You can check the migration guide:

Most G+ Sign In applications requested some combination of the scopes: plus.login, plus.me and plus.profile.emails.read.

New Scopes:

•   email (https://www.googleapis.com/auth/userinfo.email)
•   profile (https://www.googleapis.com/auth/userinfo.profile)
•   openid (https://www.googleapis.com/auth/plus.me)

It's better to switch to Google Sign-in authentication system. Google now recommends requesting an ID token and sending that ID token from your client to your server. ID tokens have cross site forgery protections built-in and also can be statically verified on your server, thus avoiding an extra API call to get user profile information from Google’s servers. Follow the instructions for validating ID tokens on your server.