What is the best / easiest way to transmit user credentials on the Transport Layer
I have two systems A and B that are connected to a third party message layer. C.
Is it any way (better than NAT) in any way can store / serial certified user credentials in any way, A, transmit it to C, then it is B-B Do D-serial but call downstream system D using the De-serialed credentials?
The Windows generated by LSA is valid only on the system on which the token was generated - if you serial a token with a system and do deserialized, then LSA will not accept it as proof that this process was authenticated by that target system and had any right to use any secure resource on the system. Speaking of roles, playing attacks again (taking safety issues from a box and running it again - maliciously or otherwise, the security threat model will not be taken into account).
The "easiest" way to do this is to prompt the user to type your username and password for your code. This is also the most common scenario in case of security related flaws, and Any right-minded organization will be stunned if their applications had something raw, but it is is a theoretical alternative.
Better to find embedded support for a certification protocol, there must be a way to inter-system communication - see GSS-API for a cross-platform API that is often useful in these references Are there.
Comments
Post a Comment