Currently, you get the platter when you might only want a side-item.
For internal projects at Ritter, we have a need to allow bearer-token auth, but disallow UI auth (and vice-versa) on our QA sites.
I propose using the StuntmanOptions-instance passed to UseStuntman to selectively enable bearer-token and UI authentication as two separate properties on the options instance (this could be combined as one property using &, but it seems overkill for only two possible values).
billbogaiv
commented
7 years ago
Currently, you get the platter when you might only want a side-item.
For internal projects at Ritter, we have a need to allow bearer-token auth, but disallow UI auth (and vice-versa) on our QA sites.
I propose using the
StuntmanOptions-instance passed toUseStuntmanto selectively enable bearer-token and UI authentication as two separate properties on the options instance (this could be combined as one property using&, but it seems overkill for only two possible values).