YahooIdentity and Access
Outside Participants Sign In With The Mail Account They Already Use
Many of the people a public body needs to reach have no work email and no reason to create another password. Volunteers, residents and outside participants often do have a Yahoo account they already use for mail. On a public-facing portal built on Nexus positioned as the Enterprise Video Platform, social sign-in puts Yahoo on the sign-in page, and a visitor who picks it arrives identified with no organizational account created for them. Yahoo keeps the password. Staff sign-in is untouched.
What you can do together
Admit people who have no work account
Volunteers and residents reach a public portal on Nexus with the Yahoo account they already use for mail, with nothing to register and no password for your help desk to reset.
Know who is watching
A visitor who signs in arrives identified rather than anonymous, so a public session has known viewers and not only traffic.
Offer the account each visitor holds
Yahoo sits beside the other consumer providers the administrator has enabled, so a visitor without a Google or Facebook account is not turned away.
Leave staff access alone
Social sign-in is licensed and enabled separately from the corporate SSO app on Nexus, so opening a public portal changes nothing internally.
How it connects
Social sign-in is licensed as its own feature and enabled per portal, separate from the corporate SSO app your staff use. Once it is on, Yahoo appears as a choice on that portal's sign-in page, connected over OAuth. The visitor authenticates at Yahoo under Yahoo's own policy and comes back signed in, so the portal never handles the password and issues nobody an organizational account.
The portal is a service provider and never becomes an identity provider. A Yahoo identity sits outside your directory and brings no groups with it, so what a signed-in visitor may see and do comes from the portal's own settings rather than from directory membership. The administrator decides once what the public side of the portal holds, and a Yahoo visitor gets what the portal grants public visitors.
Yahoo is one of the consumer providers social sign-in supports, alongside Google, Microsoft account, Facebook, LinkedIn and X. Which of them a portal offers is an administrator's decision, and it changes nothing for staff. Yahoo sign-in identifies a member of the public rather than a member of staff. It is not a route into internal content, and it adds no one to your staff directory.
YahooIdentity and Access
A scenario
- Setup, ITThe county enables Yahoo social sign-in on the public training portal and sets what a signed-in visitor may open. The staff portal keeps its corporate SSO app, licensed separately and unchanged.
- Six weeks before the electionThe training coordinator publishes the polling place check-in walkthrough to the public portal as public content.
- Thursday, 19:10A first-time poll worker opens the portal, picks Sign in with Yahoo and approves the request at Yahoo. She is watching the walkthrough moments later, and the county created no account for her.
- Same eveningAnother poll worker signs in with Google from the same page. Both arrive as identified viewers with what the county set for public visitors, because neither identity carries a county directory group.
- After election dayReconciliation procedures for permanent staff stay on the staff portal behind corporate SSO. Yahoo sign-in reaches the published training and nothing beyond it.
What stays where
Yahoo remains the visitor's identity
The account and the password belong to Yahoo and to the person. Nexus stands on the other side of that exchange as a service provider, never as an identity provider.
Your directory stays a staff directory
A Yahoo identity is outside it and carries no groups, so entitlement for these visitors, and any change to it, is set in the portal.
Nothing changes for staff
Corporate SSO is a separate app under a separate license, and enterprise portals go on enforcing sign-in to your own provider. Social sign-in serves public viewers, not employees.
The portal runs where you deploy it
Shared SaaS, a dedicated cloud, or servers you run yourself.
Products and solutions
Next step
See it on your own Yahoo instance.
We will show the connection made, the data moving and the output, then size it for your deployment.
Contact VIDIZMO
sales@vidizmo.ai
+1 571-969-2180
vidizmo.ai