The Movie Database 지원
지원 → API 지원
jsonp & api key security?
9월 22, 2012일 3:24 오후시에 happycrappySTAFFMOD님이 게시함
Hi,
I was wondering how guarded should my api key be? Is it ok to expose it to my users to be consumed by javascript (ala google maps key)? or should I consider it a private key that should only reside on serverside code?
If its the latter, whats the recommended method to implement a typeahead/autocomplete search?
Thanks
Travis Bell님의 댓글
9월 23, 2012 at 12:05 오후
This is always a tricky issue. With any public facing JavaScript project it will be impossible to obfuscate our API key. I realize there is nothing you can do about this.
Just be responsible with it, we offer our API for free so hopefully anyone wishing to use it will simply ask us for a key.
happycrappy님의 댓글
9월 23, 2012 at 1:37 오후
thanks!
rclai님의 댓글
8월 1, 2015 at 6:22 오후
Travis,
If I expose my API key in the client-side, is someone able to take it and use it somewhere else?
Travis Bell님의 댓글
8월 2, 2015 at 10:55 오전
Hi rclai,
Yes, someone would be able to. The thing to keep in mind, which is why we don't generally regard this to be a big problem is that we offer the API for free. Everyone can sign up an account and request a key themselves.
Cheers.
rclai님의 댓글
8월 2, 2015 at 6:41 오후
Thanks for the answer. I guess the IP based rate limiting helps relieve this issue too.