Fork me on GitHub
#yada
<
2017-04-27
>
borkdude18:04:09

Is it possible to protect the swagger API made by yada/swaggered using the same auth as yada resources?

malcolmsparks18:04:10

Yes. But use the 'simple' rather than 'easy' way

borkdude18:04:21

What’s the simple way?

malcolmsparks18:04:33

See the docs. Afk sorry!

malcolmsparks18:04:09

I'm sure there's a direct link ;)

malcolmsparks18:04:47

If you get stuck let me know. Summer of yada starts next week!

borkdude18:04:02

Aaah, thanks. I hadn’t seen this yet.

malcolmsparks18:04:44

(For regular listeners, the 'summer of yada' starts when I move house on May 4th and return to a regular routine of yada development)

borkdude19:04:09

Cool, it worked

dominicm19:04:14

The 4th is strong yada's one? 😜

malcolmsparks19:04:40

Begun the yada development has.

borkdude20:04:49

I have a similar question about classpath-resource and webjar-resource. Normally I can protect a resource by composing it (it’s just a map to which I can add stuff and call yada/resource on to validate). This doesn’t seem to work here. Maybe it has to do with how sub-resources work. Something for tomorrow I guess.