131–140 of 197 posts
Earlier quoted context omitted.
Or you could do the opposite and be like the company I work for. Force everyone to enter an RSA token on every SSO login.
It doesn't have to be that manual, yubikey etc can just plug and press.
The people making the policies don’t care at all. They are just dotting is and crossing ts.
Earlier quoted context omitted.
Having Azure AD does not prevent clients from also having Okta or any other 2FA provider for 2 factor authentication. In fact, I have worked with at least 10 clients in the last 2 years that used Azure AD for authentication but then something else for 2-factor depending on the type of apps. Sometimes even within one company, there are multiple 2FA protocols, e.g. using Oracle single sign on for ERP apps but Okta for…
Okta is a single sign on provider though. Clearly, authenticating via Azure and also Okta would not be single sign on.
What is Azure AD used for?
Active Directory is Microsoft's LDAP[1] server offering. Eventually it got more features and is used by firms to enforce company wide (or group wide) rules like "Every computer must lock after 5min of inactivity" or "Adobe Acrobat must be installed in all computers". Azure Active Directory is the cloud version of Active Diretory. It has some extra features compared to on prem AD (MFA, SSO with 3rd paty apps...) but t…
Earlier quoted context omitted.
In the US at least it seems like we’re at the stage where every new account created is essentially tied back to a social security number. One cannot get an e-mail address without a phone. One cannot get a phone without a credit check. A credit check requires a social security number.
Prepaid phones are readily available in the US, no ID or SSN required.
(when it doesn't work, you'll usually get an error message about the number not being supported or words to that effect)
Doesn't the end point show up once you have SSO with your own identity provider enabled for any Microsoft services? Maybe technically this means that you have an Active Directory tenant as well, but it doesn't necessarily imply that you are using those Active Directory services for anything beyond that SSO capability. For Google Workspace, a similar URL is: https://www.google.com/a/example.com/ServiceLogin
That is a big assumption though. A very well known big-four with two letters uses for instance [letters]gs.com ("Global Services") for instance.
I genuinely don't know what AD is used for. If you need SSO, why not just use a SSO/SAML IdP?
OpenID Connect seems like the current popular flavour. SAML seems to be increasingly considered legacy.
Also, SAML as a spec is really complex precisely because it was created to satisfy a broad range of Enterprise-y requirements. I don't know if OpenID Connect is there yet. It certainly could be, the underlying spec (oauth2) could support a lot of variant complexity, and OIDC supports mobile and there are lot of extensions available or in progress. https://openid.net/developers/specs/
Earlier quoted context omitted.
Honestly, I think the regulators should look at basically all of those things. Here in Europe scrutiny is building and a lot of those organisations do party hard and play loose with the rules. Microsoft is famously anticompetitive, but Adobe, Google and Apple can't be far behind in their respective areas.
Really? So you really think companies shouldn’t be able to sell software that works together bundled together? Why stop there? Phones and computers shouldn’t be “bundled” with operating systems? Computers shouldn’t be “bundled” with sound hardware? Where does it stop?
This is the answer to the question “why can’t we get rid of passwords?”
Or you could do the opposite and be like the company I work for. Force everyone to enter an RSA token on every SSO login.