Authentication

@Narf You assume too much.

No, you assume too much by thinking that authentication is something trivial.

Don't be so certain about your 100%.

I am rarely that sure about something.
Your continous ignorance towards arguments other than "there's demand for it" only serve to solidify my opinion.

I didn't graduate with honors and formally became a senior developer/engineer two years after working, just so you can arrogantly say I don't have half the knowledge to implement Authentication and Authorization flows.

Really? I suggest you carefully read what I said:

I am 100% certain that you don't have half the knowledge necessary to build a secure authentication/authorization library. Yet you claim it isn't difficult.
The fact that you can easily build something that works doesn't meant that it is secure.

... very specifically emphasising on the word "secure", and also very specifically noting that building something that works doesn't mean you've built it to be secure. I had no doubt that you can build some "flow" that works, and I very carefully worded my reply to say that it merely working is not the problem at all.

You're way beyond twisting my words.

Also, I don't care about your diploma or job title as they've got little to do with security.

And as I said implement (to use), and not create (from scratch). Get the difference? You consistently assume too much.

Did you notice that I said "had no doubt" above? That's because you're now saying that you can't even implement this from scratch yourself.

You're saying you can't build something that you've at the same time claimed was "not difficult" ... Know how that's called? Making assumptions.

Going back to the request, it's about creating bare bones Auth structures that CI4 can call its own.

That means you think one such structure fits all implementations, even though you don't know what the implementations would be.
Assumptions.