Why setUserIdentifier, not setUser? about oauth2-server HOT 9 CLOSED

I also wonder why the User entity is not passed instead the identifier . This one is used only here:

vendor/league/oauth2-server/src/Grant/AbstractGrant.php

    protected function issueAuthCode(
        DateInterval $authCodeTTL,
        ClientEntityInterface $client,
        $userIdentifier,
        $redirectUri,
        array $scopes = []
    ) {
        $maxGenerationAttempts = self::MAX_RANDOM_TOKEN_GENERATION_ATTEMPTS;

        $authCode = $this->authCodeRepository->getNewAuthCode();
        $authCode->setExpiryDateTime((new DateTimeImmutable())->add($authCodeTTL));
        $authCode->setClient($client);
        $authCode->setUserIdentifier($userIdentifier);

vendor/league/oauth2-server/src/Grant/AuthCodeGrant.php

        if ($authorizationRequest->isAuthorizationApproved() === true) {
            $authCode = $this->issueAuthCode(
                $this->authCodeTTL,
                $authorizationRequest->getClient(),
                $authorizationRequest->getUser()->getIdentifier(),
                $authorizationRequest->getRedirectUri(),
                $authorizationRequest->getScopes()

And it looks like there is no problem to pass the whole User entity.
On the other hand the current behavior, i.e. using the identifier allows loading the users from somewhere else which I guess is the main idea behind this.

from oauth2-server.

Have you looked at the bundle for Symfony? It might be easier to integrate with your application using it

from oauth2-server.

@Sephster Unfortunately, we cannot use it as we have old Symfony version and not updated yet. But it's a good idea to look there for a workaround, thanks.

from oauth2-server.

@Sephster I see that the Symfony bundle doesn't make any foreign keys in the persistense entities and just fills DB with schema initialization code. It doesn't suit our requirements, we should make database manipulations with migrations.

I just can't understand why in this particular field you don't operate interface and use id. It doesn't make any sense for me.

from oauth2-server.

I can't speak as to why the code is like that as I didn't write the lines you are referencing. I am not sure why this would have such a bearing on your application code though. Are you able to share example code?

I believe people have successfully implemented this lib using Doctrine as the backend in the past as this issue hasn't been raised before so I'm hoping the fix can be done in userland rather than this codebase if possible

from oauth2-server.

Of course, I already found a workaround, but it looks a bit ugly.

from oauth2-server.

@sgoranov yes, I'm talking about the same: always when we're going to link accessToken/authCode to a user, we can pass User entity either and loose nothing. But looks like the code base already cannot be adapted for this, and it will break backward compatibility.

I only wanted to know what decision brought developers to this and understand the solution.

from oauth2-server.

The original developer of this is no longer involved in the project so I can't speak as to why it was implemented that way. Do you have a link to the Doctrine behaviour stating you must pass an object to create a relation? Thanks

from oauth2-server.

Closing due to lack of response

from oauth2-server.