!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rule 1- All posts must be legitimate questions. All post titles must include a question.
All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.
Rule 2- Your question subject cannot be illegal or NSFW material.
Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding META posts and joke questions.
Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.
On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.
If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.
Rule 7- You can't intentionally annoy, mock, or harass other members.
If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.
Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- Majority of bots aren't allowed to participate here. This includes using AI responses and summaries.
Our breathtaking icon was bestowed upon us by @Cevilia!
The greatest banner of all time: by @TheOneWithTheHair!
This is called an identity first workflow and is used specifically so that they can route different people to different login ceremonies or providers.
They get your id first, and use that id to determine what your login ceremony is. Perhaps you’re with a business that they have an sso integration with and will send you on to your businesses sso provider, or perhaps you’re a local user for them and get a password screen next.
login ceremony
What pretentious asshole came up with that bit of jargon?
Me…
I will steal it for work without giving credit! Thanks!
Do it! I work in the industry and have found it to be very effective in conversations spanning varying levels of technical expertise.
I love it
Lol I've never heard that term but it actually does kind of work. Auth is something that is very standardised with it's communication between the FE and BE so the login flow could be compared to a ceremony. Kind of a silly way to describe it though
I'm sure we can work daemons in somehow
That doesn't explain why my Synology NAS does it, though, because I don't believe the web portal has the ability to handle different authentication flows.
I think it might also be a barrier against brute force attacks.
Synology offers cloud services and business level support for their enterprise products. They do support different authentication workflows, they are just not all included with the consumer products.
I've never used Synology stuff but it could be future proofing or a default feature of the authentication service/provider they're using (if they are using one).
For a NAS, it actually seems like something corporate customers would very much want to have SSO support for so I'd actually be surprised if there wasn't some way to set it up already
identity first workflow and is used specifically so that they can route different people to different login [hamster wheels]
The one thing MADE for JavaScript and no.
It's often implemented with JavaScript, yes
This is generally done when you have customers with SSO, the first one will take the email and if the domain is ssod it forces them through a particular workflow. Otherwise you get the other normal username/password flow
Different domains need different authentication flows. If the provided email ends in a domain they recognize, instead of prompting for a password you’d be sent to another auth provider to authenticate there.
This is usually the right answer. In the past, logging in was a simple pipeline with no forks along the way. That’s why a simple username + password did the trick. Nowadays, logging in has become a complicated journey with several ways to get to the destination. Once the site knows your email, it knows what’s the next step in your case.
Sometimes it's just UI/UX, sometimes it's to deter specific patterns they've seen from bots, users, or brute-force. It's really just subjective. One isn't necessarily better than the others though it does mess with automated input of credentials a lot of times.
I always assumed some sites harvest what ever you enter in the first box. Especially if it’s an email address. But other people in this thread have the legitimate answer.
Some sites check if the account does not exist yet to show a registration form.
its called "enshitification"
there's a book about it