• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 189
  • Last Modified:

Credential Checking

There are many format standards for web services (XML, JSON, etc),.  There seems to be a lot of legacy apps using XML, but most of the energy seems to be moving towards JSON.

What I need to implement now is some sort of identity protection, and I have little experience in this.  What is the most common form (SAML, Kerberos, etc) that will pass basic (nothing fancy) credentials?  Is there a standard that is developing momentum (like JSON).

Anthony Lucia
Anthony Lucia
2 Solutions
greetings Anthony Lucia, , I am only posting here because no other EE expert has, , I have done some web , I guess you can call them "services", for Server clients, to  establish an account, and are given server code that is used to get the services provided by doing a protocol (http, rest) exchanges.
The problem I have when I read your question is how little information you give about your "web service" and the factors you may want to implement in the web service to have to (in your words) - "I need to implement now is some sort of identity protection"  and the use of "XML" or "JSON" in the "identity protection" of some (maybe all) data exchanges to and from your http server exchange service. You may can re-ask this question with more info about the server exchange protocols (rest, soap, connection) and the ways you need to have your service deliver information, , and you might get some much better expert advice? ?
The easiest would be to implement basic authentication.

Featured Post

Put Machine Learning to Work--Protect Your Clients

Machine learning means Smarter Cybersecurity™ Solutions.
As technology continues to advance, managing and analyzing massive data sets just can’t be accomplished by humans alone. It requires huge amounts of memory and storage, as well as the high-speed power of the cloud.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now