Some advice on how to even properly describe these relationships would be a great start. Something accurately described is a problem looking for a solution. I have entities User and Login, where Login describes basically a login session for one user. So, User normally has many Login instances. This relationship is only described on the Login side with a required, single User navigation property, and there is an implied, but not declared, Login collection on the User side.
Then, for the other relationship, a User is created under authorization of a Login, so this relationship is described on the User side, with a Login navigation property, and there is an implied, but not User collection on the Login side.
I don't do much DB modelling outside of using the DB tools, and they always just get relationships right for me, but now, I have to map these relationships for code first, using fluent mapping. How do I described these two relationships, what are the principle and dependent sides, and what are the multiplicities here?