Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
For a sign-in-only OpenID Connect request, the protocol-level scope is openid. Add profile or email only if the application needs those additional claims; do not request unrelated API or resource permissions for authentication. These are OpenID Connect scope examples, not verified Waaseyaa configuration syntax: the available Waaseyaa package documentation does not identify the client-side setting or code path for scopes.
Choose scopes by the identity claims you need
OpenID Connect (OIDC) adds an identity layer to OAuth 2.0. As the OpenID Connect Core 1.0 specification puts it, “OpenID Connect implements authentication as an extension to the OAuth 2.0 authorization process.” The openid scope identifies an OIDC authentication request; OAuth 2.0 by itself does not define this standard identity layer.
| Protocol-level scope | When to request it |
|---|---|
openid |
For an OIDC sign-in request and identity. |
profile |
When the application needs additional profile claims. |
email |
When the application needs email-related claims. |
address |
When the application needs address claims. |
phone |
When the application needs phone claims. |
OIDC scopes are space-delimited and case-sensitive. For an application that needs both profile and email claims, openid profile email is a protocol-level example. If it needs only an OIDC identity, request openid. Neither example establishes the accepted scopes or configuration syntax of a particular Waaseyaa deployment. Keep identity claims separate from scopes that authorize access to APIs or other user data, and request only the claims the experience actually uses.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →How the Waaseyaa packages fit together
The Packagist listing describes waaseyaa/oidc as the Waaseyaa ecosystem’s OpenID Connect issuer. It says the issuer primitives are used by a dedicated identity-provider app, while consumer applications federate through waaseyaa/oauth-provider and its GenericOidcProvider. The listed issuer surface includes authorization, token, UserInfo and discovery endpoints, JWKS, revocation, RP-initiated logout, and signing-key storage and rotation. The listing also says consumer apps do not install the issuer package.
#1 Best Overall
- POWERFUL SECURITY KEY: The Security Key C NFC is the essential physical passkey for protecting your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with Google, Microsoft, and Apple. A single Security Key C NFC secures 100 of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your Security Key C NFC via USB-C and tap it, or tap it against your phone (NFC) to authenticate. No batteries, no internet connection, and no extra fees required.
- TRUSTED PASSKEY TECHNOLOGY: Uses the latest passkey standards (FIDO2/WebAuthn & FIDO U2F) but does not support One-Time Passwords. For complex needs, check out the YubiKey 5 Series.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
This distinction matters when locating the scope request: the issuer package and the consumer’s federation integration are different roles. The package listing does not say whether a consumer sets requested scopes in a configuration file, provider constructor, authorization-request builder, or another layer. It therefore does not support a Waaseyaa-specific code sample or option name.
What is and is not established for Waaseyaa configuration
The exact client-side scope setting is undocumented in the available package listing. No specific configuration key, class API, or client code path can be confirmed from it. Before changing a live integration, check the documentation and source for the exact installed consumer and issuer versions, and identify which component constructs the authorization request. Do not assume a generic OAuth setting name applies to Waaseyaa.
Rank #2
- POWERFUL SECURITY KEY: The YubiKey 5C NFC is the most versatile physical passkey, protecting your digital life from phishing attacks. It ensures only you can access your accounts
- WORKS WITH 1000+ ACCOUNTS: Compatible with popular accounts like Google, Microsoft, and Apple. A single YubiKey 5C NFC secures 100+ of your favorite accounts, including email, password managers, and more
- FAST & CONVENIENT LOGIN: Plug in your YubiKey 5C NFC via USB and tap it, or tap it against your phone (NFC), to authenticate. No batteries, no internet connection, and no extra fees required
- MOST SECURE PASSKEY: Supports FIDO2/WebAuthn, FIDO U2F, Yubico OTP, OATH-TOTP/HOTP, Smart card (PIV), and OpenPGP. That means it’s versatile, working almost anywhere you need it
- PRIMARY & SPARE KEYS: Just like having a spare house key, we recommend buying two YubiKeys - one for daily use and one as a spare. That way you’ll never get locked out of your accounts
The listing records release v0.1.0-alpha.271, published 2026-07-20. At its 2026 capture, it displayed 2,696 installs and 4 dependents. Those are dynamic Packagist counters, not evidence of active production deployments or authentication volume.
Keep the authorization request focused and safe
Once you have identified the component that builds the request, keep identity scopes distinct from resource permissions and apply ordinary request safeguards. Google’s web-server OAuth documentation provides provider-specific examples; these examples describe Google’s implementation, not verified Waaseyaa defaults.
Rank #3
- POWERFUL SECURITY KEY: The YubiKey 5 NFC is the most versatile physical passkey, protecting your digital life from phishing attacks. It ensures only you can access your accounts
- WORKS WITH 1000+ ACCOUNTS: Compatible with popular accounts like Google, Microsoft, and Apple. A single YubiKey 5 NFC secures 100+ of your favorite accounts, including email, password managers, and more
- FAST & CONVENIENT LOGIN: Plug in your YubiKey 5 NFC via USB and tap it, or tap it against your phone (NFC), to authenticate. No batteries, no internet connection, and no extra fees required
- MOST SECURE PASSKEY: Supports FIDO2/WebAuthn, FIDO U2F, Yubico OTP, OATH-TOTP/HOTP, Smart card (PIV), and OpenPGP. That means it’s versatile, working almost anywhere you need it
- PRIMARY & SPARE KEYS: Just like having a spare house key, we recommend buying two YubiKeys - one for daily use and one as a spare. That way you’ll never get locked out of your accounts
- Request only needed scopes. Use a space-delimited scope list and avoid unrelated API permissions when the application only needs sign-in.
- Match the redirect URI exactly. In Google’s web-server implementation, the scheme, letter case, and trailing slash must match the authorized URI.
- Use and validate
state. It correlates the authorization response with the originating request and helps mitigate CSRF.
For these provider-specific request details, see Google’s web-server OAuth documentation.
Decide separately whether offline access is necessary
Offline access is not an identity scope. Google documents access_type=offline for applications that need to refresh access while the user is absent; its authorization-code flow can return refresh tokens in that case. A sign-in-only requirement is not, on its own, a reason to request offline access. Whether and how refresh access works in a Waaseyaa integration must be checked against the actual consumer and issuer versions.
Rank #4
- POWERFUL SECURITY KEY: The Security Key NFC is the essential physical passkey for protecting your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with Google, Microsoft, and Apple. A single Security Key NFC secures 100 of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your Security Key NFC via USB-A and tap it, or tap it against your phone (NFC) to authenticate. No batteries, no internet connection, and no extra fees required.
- TRUSTED PASSKEY TECHNOLOGY: Uses the latest passkey standards (FIDO2/WebAuthn & FIDO U2F) but does not support One-Time Passwords. For complex needs, check out the YubiKey 5 Series.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
A practical scope decision
- List the claims the sign-in experience uses. If it needs only an OIDC identity, the protocol-level scope is
openid. Addprofileoremailonly when those claims are needed;addressandphoneare further optional claim scopes. - Remove unrelated resource permissions. Do not conflate identity claims with authorization to call APIs or access other user data.
- Locate the request owner in your integration. Determine whether the consumer application or a provider integration constructs the authorization request; the package listing establishes the issuer/consumer roles but not the scope-setting API.
- Verify the version-specific implementation. Consult the documentation or source for the installed version before adding configuration or code. Treat the scope strings above as OIDC protocol guidance, not a tested Waaseyaa snippet.
- Assess refresh needs independently. Add offline-access behavior only if the application genuinely needs to refresh access while the user is absent, and verify the provider-specific mechanism.
Google likewise classifies openid, profile, and email as authentication-only scopes in its own environment and suggests considering Sign In With Google and an ID Token when those are the only scopes a Google-integrated application needs. That is Google-specific guidance, not a rule for configuring Waaseyaa’s OIDC issuer. See Google Identity Services.
Quick Recap
Best Value
- Security Key : Protect your online accounts against unauthorized access by using FIDO2 and U2F authentication with T110. It's the world's most protective security key that works with windows, Mac OS, Linux as well as Chrome, Firefox, Edge and many other major browsers.
- Certified with the new FIDO2 standard, T110 provides the benefit of fast login and strong protection against phishing, account takeover as well as many other online attactks.
- Works with : Bank of America, Github, Google, Microsoft, DUO, Twitter, Facebook, Dropbox, Apple, ebay, BINANCE, mor and more.
- Fits USB-A port : Insert the T110 security key into the USB-A port of each service and log in conveniently with one touch
- For the driver download and user guide, please visit TrustKey Solutions Home support page.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
