I think, it depends on what kind of server-side technology do you use.I'm using normally REST APIs with Spring Boot and for that part I use Spring Security with OAuth2 / JWT token.But the simplest one would be using Spring Boot and Spring Security like this example: https://spring.io/guides/gs/securing-webHope this helps!ime...@gmail.com schrieb am Mittwoch, 21. Oktober 2020 um 20:56:10 UTC+2:Are there best practices for securing RPC calls? In an app I'm working on some of the calls are OK to go through without authentication, and some do require authentication and authorization. Any thoughts / suggestions?Slava--
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/f_QJldsQ-y0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/e154fd85-7841-4a74-ac36-e7461c71a498n%40googlegroups.com.
Wednesday, October 21, 2020
Re: Securiring GWT-RPC calls?
It's Java + Tomcat + GWT service servlet.