-5

I'm looking for failures in this "token based login" design, besides the UML "syntax" errors. Theoretically speaking, it will do the trick when implemented on an small project.

If true, sorry about my english.

Thaks in advance.

EDIT: Is 1) this model something useful and clear? 2) Will it work when implemented? 3) Besides the implementation, is secure?

Token based authentication sequence diagrams

closed as unclear what you're asking by Ben Cottrell, gnat, David Arno, Greg Burghardt, BobDalgleish Jan 23 at 14:00

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • I am glad that you are looking for failures in your protocol. What is your question about this protocol? – Kain0_0 Jan 11 at 4:33
  • Kain0_0 thanks for commenting. I've edited the post adding some questions that concern me. – Marcelo Jan 12 at 16:53
  • What are your attack vectors? What parts of the communication are vulnerable to man-in-the-middle attacks, replay attacks? You have to ask detailed questions before you can get useful answers. – BobDalgleish Jan 23 at 14:02
0
  1. Useful and clear will depend on who you are communicating with and about what. This appears to be a reasonable diagram with which to discuss how authentication occurs in a particular application.

  2. Work when implemented? I'm not sure how good your team is about filling in the missing details surrounding this diagram. If they are good, the resulting code may be operational. Taking a guess, I believe you mean work as in achieve the intended function? That will depend on the specifics of what you consider functional. I find the User-Password path reasonable, I have questions about how the Token is being implemented.

  3. If you want security, throw this out and find a model deemed secure by the cryptographic/security community. As an aside you can dabble in this, but even seasoned professional security experts have trouble defining a secure system from the ground up. If this is going anywhere near a production environment do not make your own. Find and use tried and tested implementations, or at worst find tried and tested approaches, and have your implementation studied intensely for vulnerabilities.

My specific questions about your token system boil down to:

  • Why are you persisting the token locally? The point of a token is for it to be validatable without checking back with the authoriser.
  • Why are the password hashes being stored in the token? This is not a good idea.
  • How are you encrypting the token? This is important for security.
  • Have you considered how to defend the token against replay attacks? This is important to prevent fraud.
  • Have you looked at other token based architectures?
  • Thank you very much for your elaborated answer. Now It's clear that I need do more research about this. Passwords hashes are not being included in any way on the token. I don't know yet how to encrypt the token. Respecting the replay attack question, the token is for one use only, then is discarted -It'll be stripped of its authorization powers-. I've looked just with one eye the general schema, nothing deep. Thanks again for your knowledge. – Marcelo Jan 27 at 22:28

Not the answer you're looking for? Browse other questions tagged or ask your own question.