Skip to content
This repository has been archived by the owner on Apr 20, 2021. It is now read-only.

Can't add header Authorization for jwt token #266

Open
ehibes opened this issue Oct 23, 2018 · 6 comments
Open

Can't add header Authorization for jwt token #266

ehibes opened this issue Oct 23, 2018 · 6 comments

Comments

@ehibes
Copy link

ehibes commented Oct 23, 2018

Hi,

I'm trying to login to an API before execute some behat tests with this function. It seems not to accept the header.

/**
 * @BeforeScenario @login
 *
 */
public function login(BeforeScenarioScope $scope)
{
    $user = $this->doctrine->getManager()->getRepository('App:User')->findOneByEmail('test@test.com');

    $token = $this->jwtManager->create($user);

    $this->restContext = $scope->getEnvironment()->getContext(RestContext::class);
    $this->restContext->iAddHeaderEqualTo('Authorization', "Bearer $token");
    $this->restContext->printLastResponseHeaders();
}

The last line return following output, where authorization header is missing

content-type: application/ld+json; charset=utf-8
x-content-type-options: nosniff
x-frame-options: deny
cache-control: no-cache, private
date: Tue, 23 Oct 2018 15:58:14 GMT
link: <https://localhost/api/docs.jsonld>; rel="http://www.w3.org/ns/hydra/core#apiDocumentation"
@B-Galati
Copy link

Hello,

You are printing the response headers instead of the request.
On my end, I used this context for the authorization header and it was working great.

@ehibes
Copy link
Author

ehibes commented Oct 23, 2018

Ok for the response but executing this scenario and testing header return Behatch\Context\RestContext::theHeaderShouldContain() The header 'authorization' doesn't exist (OutOfBoundsException)

  @login
  Scenario: Create a result as admin
    When I add "Content-Type" header equal to "application/ld+json"
    And I add "Accept" header equal to "application/ld+json"
    And the header "Authorization" should contain "Bearer"
    And I send a "POST" request to "/api/results" with body:

@B-Galati
Copy link

I guess (not sure) it's because $scope->getEnvironment()->getContext(RestContext::class) returns a new instance of RestContext.
You can try to extend Behatch RestContext and use this new class in your context configuration instead of the one from Behatch.
A bit like this https://www.bgalati.fr/blog/php-matcher-with-behat-to-assert-unpredictable-json/.

@ehibes
Copy link
Author

ehibes commented Oct 25, 2018

There is a context problem for sure, following features don't work either and return the same output :
Behatch\Context\RestContext::theHeaderShouldContain() The header 'authorization' doesn't exist (OutOfBoundsException)

When I add "Content-Type" header equal to "application/ld+json"
And I add "Accept" header equal to "application/ld+json"
And I add "Authorization" header equal to "Bearer token"
And the header "Authorization" should contain "Bearer"

@ehibes
Copy link
Author

ehibes commented Oct 29, 2018

I found the bug. When I put @logout annotation anywhere in my features, the authorization header is missing, even if a @login annotation is present on next scenario.

/**
 * @BeforeScenario @logout
 */
public function logout() {
    $this->restContext->iAddHeaderEqualTo('Authorization', '');
}

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants