stormpath / stormpath-framework-tck

HTTP integration tests that ensure a Stormpath web framework integration implements the Stormpath Framework Specification

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

ErrorsIT has hardcoded realm

bdemers opened this issue · comments

Link to current version of file:

.header("WWW-Authenticate", "Bearer realm=\"My Application\"")

.header("WWW-Authenticate", "Bearer realm=\"My Application\"")
I was testing with an application that was not named the default My Application, and the ErrorsIT failed.

Simple work around: use a different application, or rename an existing one.

The simple workaround is fine right now (for me at least), but this will be a problem when we get to the point of the TCK testing multiple configurations/applications.

Is the solution to make the TCK read some config or env var that contains the expected name of the application? That would work, but feels icky to me.

Or just read the app name from Stormpath

Or just read the app name from Stormpath

Assuming a dependency on STORMPATH_APPLICATION_HREF?