Steps 5-10 are pretty specific to my setup, but they stand as a good example of how you will configure multiple authenticators and identifiers that will be used sequentially later during authentication checks.
The class labeled ConcreteAuthenticatior represents the Authenticators loaded in steps 5-8. They will be tried in sequence unless one of them succeeds and returns through step 16. Each one will try all the configured Identifiers in sequence.
Of special interest to me was step 22 where any custom Identifier object you design gets put into play. Having an object with a little more knowledge than just the user record is quite handy.
It helps to see how the process proceeds step-by-step, that’s what’s meant for, that’s ok.
In order to get my questions answered, I have to map this diagram on the used CakePHP-files (for example, application.php etc.) to get an idea where at what place to change things to get the desired result. Because I’m a noob, I’ve no idea.
In case of my search to find how the get unauthenticated acces to ‘local:8765’, it’s in step 17 I guess? And now I have to figure out in what file to use what command. I’m not that familiar with UML, but is there a way to connect this diagram with how the steps are implemented?
I’v drawn a lot of diagrams, it’s my experience that it’s always about scope and purpose which determine the level of detail.
Scope in how it fits between existing diagrams, like for instance high level CakePHP at a Glance - 4.x and Middleware - 3.10 (even if these are not UML, how do these diagrams relate? Maybe some extra (UML)-diagrams needed, maybe it’s ok now?
Purpose in who’s the reader and what is s(he) looking for? Manager, NOOB, core-developer, debugger, student, programmer? All of them will need another level of detail.
And in the end? 99% of the diagrams were only used by myself to organize my thoughts, to get things clear to myself. Just to be able to discuss things with managers, analists, developers.