A seller's tool login can skip your password policy when its password is hash-set, reset by hand, or signed in through OIDC. A new seller's account can be created with any of these paths, so check the creation path before you assume the policy applies.
Key takeaways: where a seller login slips past
- Check how each seller's tool login is created before the seller's first day.
- Record each hash-set, manually reset and OIDC login as its own path, because the policy does not check it.
- Record whether each tool uses OIDC or SAML sign-in before you rely on a policy for that seller.
- Match your own settings to the AD and LDAP minimums for directory-sourced users.
Why a new seller's login can skip your password policy
A new seller may need logins to several tools on the first day, and each login may be created in a different way. Some accounts are added in batches, some are created one at a time by an admin, and some come from a directory your company already runs. When you set a password policy, you set a rule for one system. Before you assume it covers the seller, ask which accounts that rule actually reaches.
Start with the question of who creates each login. The person who sets up a tool account may be a front-line manager, a colleague with admin access, or an automated sync, and the path affects which checks you can rely on. Write the creator's name or role next to each tool, so the record shows how the account was made and not only the policy you intended to apply. Keep this note with the seller's onboarding file.
Use two lists rather than one. The first list names every tool a seller must use. The second list names how each tool's password gets set, reset, or signed in. A single list of tools can look complete while the password path is missing, so read the second list before you approve a seller's access. Mark any tool where you cannot find the path, and ask the tool's administrator in writing.
Do not assume that one policy setting governs every sign-in path. Each path in this guide is set, reset, or checked differently, so each one needs its own line in your notes. This is editorial advice rather than a description of any product's behavior. Before you rely on a path, confirm it with that tool's own documentation or support team, and write down the date you checked.
Write the sign-in path for each tool before the seller's first working day, so the check happens before access is granted. A short written note also helps the next manager who takes over onboarding, because they do not have to rebuild your decisions. Keep it simple: tool name, creation path, who did it, and the date. A record kept current is easier to trust than one reconstructed after a problem.
Before day one: check how the account is created
Open a blank note for each seller and list every tool login they need on day one. For each entry, record how the password is set: a bulk user upload, the Directory API, a sync tool, a manual reset, a third-party IdP sign-in, or an AD or LDAP source. Use those words exactly so every note reads the same way. Mark the path as unknown when you cannot confirm it, and do not guess. An unknown path is a question to resolve before access starts.
NIST describes its guidance as a document that "provides requirements to credential service providers (CSPs) for remote user authentication at each of three authentication assurance levels (AALs)," according to NIST. You can read that as a reference for how authentication strength is described, not as a rule your sales team must meet. Write the NIST term beside any tool whose sign-in you describe, so your note uses the same vocabulary as the source. Keep that note short and plain.
One level in that guidance is described this way: "AAL1 requires only single-factor authentication using a wide range of available authentication technologies," according to NIST. When you record a tool, note whether its sign-in is single-factor, and use the tool's own documentation as the source for that note. Do not record single-factor sign-in from memory. Write the date you read the documentation next to the note.
The guidance says applications assessed at AAL2 "must offer a phishing-resistant authentication," according to NIST. Ask each tool's provider, in writing, whether its sign-in is phishing-resistant, and file the reply with the seller's record. If the provider does not answer in writing, mark the sign-in as unconfirmed. Do not assume an answer from a tool's marketing pages. Keep the reply with the date it arrived.
A third level is described this way: "Authentication at AAL3 is based on the proof of possession of a key through the use of a public-key cryptographic protocol," according to NIST. The same guidance says federal agencies "SHALL select a minimum of AAL2 when personal information is made available online," according to NIST. That line is written for federal agencies, so treat it as a reference point and not a rule for a small sales team. Your team can still use the wording to describe sign-ins in its own notes.
Illustrative example: one seller's day-one logins
A new seller needs 3 tool logins on day one. The first is created with a bulk user upload, so its password is hash-set and the strength and length checks do not apply. The second is reset by hand after the seller forgets the password, so the policy does not reach that reset. The third signs in through a third-party IdP using OIDC, so the configured policy does not apply. Give each login its own line with the creation path, who did it, and the date.
Passwords set with a hash method
Hash-set passwords
Google says it "can't enforce password strength and length requirements on passwords set using a hash method," according to Google. The page gives examples: passwords created with the bulk user upload tool, with the Directory API, or with sync tools such as Password Sync or Google Cloud Directory Sync. Each of these is a path to note in your record.
If a seller's password came from a bulk user upload, mark that login in your record as a hash-set path. Write down who ran the upload and the date it ran. Do not treat the upload as checked by the password policy. The note tells the next person what the check did not cover.
The page lists sync tools alongside the bulk upload and the Directory API, so treat a synced account as a hash-set path to check, not as an exception. Ask whoever runs the sync which tool it uses, and record that answer beside the seller. If the answer is unclear, mark the account as unconfirmed until someone confirms it in writing.
Do not let a configured policy convince you that a hash-set password was checked. You need a separate note for each bulk or synced account. Keep those notes in the seller file alongside the account details, so the path sits next to the login it describes.
As an editorial choice, you can ask a seller to choose a new password in their first session after a hash-set setup, and write down that you asked. This step is your own choice, not a requirement from the source. Record whether the seller completed it, so your notes show what happened and not only what you planned.
Passwords you reset by hand
Manual resets
Google says "Password strength and length requirements don't apply to any user passwords that you reset manually," according to Google. That sentence covers the reset itself, so a password you type in during a reset sits outside those checks. Your own judgment about how strong the new password looks is not the same as the policy check, and your note should say which one you relied on.
Write a line in the seller's record each time you reset a password by hand. Include the tool name, the date, and the reason for the reset. A reset with no note is easy to forget, and the record then shows only the first setup. Keep the line in the same place as the bulk or synced setup notes, so the seller has one history for every login.
Name one person who handles manual resets for new sellers, so the reset list has a single owner. Tell that person which tools are in scope for your team, and ask them to add each reset to the seller record before the new password is shared. This is an editorial choice, not a requirement stated by the source, and it keeps the list easy to review.
When a seller forgets a password on day one, treat the reset as part of their history and write it down in the same format as the first setup. Note the tool, the date, and the reason. A reset recorded in the same format is easier to compare with the original setup later, which is the point of keeping both in one place. For a lockout tied to a lost phone, see lost seller phone recovery.
As an editorial choice, you can ask the seller to pick their own new password after a manual reset, and record that you asked. Choose one approach for every reset, so the notes stay comparable across sellers. Review the reset list when you have a full set of notes, and look for any reset that has no matching line.
Sign-in through a third-party IdP using OIDC, and how SAML differs
OIDC sign-in through a third-party IdP
Google says the password policies you configure do not apply when users authenticate through a third-party IdP using OIDC, according to Google. Read that sentence as a limit on the policy itself, not as a note about the seller's personal password. The same tool can sit behind either sign-in path, so your record should name the path and not just the tool.
The same page adds that "Password policies are currently enforced if you’re using a SAML IdP," according to Google. The word currently signals that the page describes a present state, so check it again when you review your setup. Do not carry the SAML statement into your notes as a permanent fact.
Put OIDC and SAML sign-ins on separate lines in your record. A login that goes through OIDC and one that goes through SAML get different notes, even when the tool name is the same. Use the sign-in type as the field that drives the note, and keep the tool name as a label only, so a reader can tell the two apart at a glance.
Two sellers can use the same tool and still reach it through different sign-in paths. That is why the path belongs in each seller's record instead of in one tool entry for the whole team. Ask each seller how they sign in on their first day, and write the answer down next to the tool they use.
Ask your team which identity provider each tool uses and whether that sign-in is OIDC or SAML. Write the answer before the seller's first login, and mark any tool where the answer is unclear as unconfirmed. An unconfirmed path should stay open until someone confirms it in writing, and the seller should not be treated as covered by a policy you have not verified.
AD and LDAP users, plus what to keep on file
AD and LDAP-sourced users
Okta says, "For Active Directory (AD) and LDAP-sourced users, AD and LDAP set and enforce these requirements," according to Okta. For those accounts, the requirements come from the directory, so the first question is what the directory enforces. Write that down before you set anything in another tool, so the directory is the reference point for the seller's login.
The same page says, "Ensure that the settings here duplicate the minimum settings of AD and LDAP," according to Okta. The sentence tells you what to match, which is the minimum settings in AD and LDAP. Copy those minimum settings into your own notes, so you can compare them with the sign-in settings you record for each tool.
Keep the copy with the seller's record and label it with the directory it came from. Write the date you copied it. A copy without a date is hard to check later, so the date is part of the record and not an extra detail. Store the copy where the seller's other onboarding notes sit, so the next reviewer finds it without searching.
Compare the copy with the directory again whenever someone changes the minimum settings there. Do not rely on memory for those settings, because a change you did not record will leave the copy out of date. Mark an out-of-date copy as out of date and replace it with a new dated copy when the directory changes.
If a seller has accounts from both directory-sourced and hash-set paths, keep both kinds of note in the same record. The two kinds of note answer different questions, so do not merge them into one line. Read each note against the tool it describes before you approve access for that seller.
Source wording at a glance
The table below sets each publisher's wording beside the scope that wording gives.
| Publisher | Source | Wording | Scope in the quote |
|---|---|---|---|
| Okta | Configure a password policy | "For Active Directory (AD) and LDAP-sourced users, AD and LDAP set and enforce these requirements." | Active Directory and LDAP-sourced users |
| Enforce and monitor password requirements for users | The password policies you configure do not apply when users authenticate through a third-party IdP using OIDC. | Users who authenticate through a third-party IdP using OIDC | |
| NIST | NIST guidance on remote user authentication | "AAL1 requires only single-factor authentication using a wide range of available authentication technologies." | AAL1 authentication |
Related guides
Your next step
Today, list each tool login a new seller needs on day one, and mark which of the three paths above it uses: hash-set, manual reset or OIDC sign-in. Start with the accounts you set up first.
Related guides: Form I-9 timing: 3 checks for a new seller · New-seller onboarding time: track it with 3 milestone parts · Check the $680 poster penalty before a new seller starts.
FAQ: password policies and new seller logins
Does a password I reset manually have to meet strength rules?
Manual resets fall outside the strength and length rules, according to Google. Treat that as the source's statement about its own policies, not as a general rule for every tool. Record each manual reset on its own line, and do not assume the policy checked it.
Do Google password policies apply to OIDC sign-in?
No. The policies you configure do not reach users who authenticate through a third-party IdP using OIDC, according to Google. Record the sign-in type for each tool before you rely on a policy for that seller.
Who enforces password requirements for AD and LDAP users?
For Active Directory (AD) and LDAP-sourced users, AD and LDAP set and enforce these requirements, according to Okta. Keep a dated copy of the minimum settings with the seller's record.
What are NIST's authentication assurance levels?
NIST's guidance describes levels of authentication assurance, AAL1 through AAL3, according to NIST. AAL1 uses only single-factor sign-in, according to NIST. Authentication at AAL3 relies on proof of possession of a key, according to NIST. Treat these levels as reference points for describing your own sign-ins, not as rules your team must meet.
Does a password policy need to rule out weak passwords?
Google's page lists a requirement that a password not be a commonly used weak password, like 123456 or password123, according to Google. As an editorial recommendation, your policy should rule out commonly used weak passwords such as those examples. Check whether the policy you set includes that rule before you rely on it for a seller.
Can Google enforce strength rules on bulk-uploaded passwords?
No. Google says it cannot enforce strength and length rules on passwords created through the bulk user upload tool, the Directory API, or sync tools, according to Google. Those examples are listed on the same page as hash-set paths. Write each of those accounts on its own line in your notes.