Authentication Algo keeps record of the Confidentiality algo

The confidentiality algo negotiated during Open Session Request
would be stored in the Authentication algorithm and is activated
once the session setup is successful.

Change-Id: I4d5efd71a992dd0cf505bcf7a6d9ebb394bcb880
Signed-off-by: Tom Joseph <tomjoseph@in.ibm.com>
diff --git a/sessions_manager.cpp b/sessions_manager.cpp
index c4de59f..18c96ba 100644
--- a/sessions_manager.cpp
+++ b/sessions_manager.cpp
@@ -26,7 +26,8 @@
 
 std::weak_ptr<Session> Manager::startSession(SessionID remoteConsoleSessID,
         Privilege priv, cipher::rakp_auth::Algorithms authAlgo,
-        cipher::integrity::Algorithms intAlgo)
+        cipher::integrity::Algorithms intAlgo,
+        cipher::crypt::Algorithms cryptAlgo)
 {
     std::shared_ptr<Session> session = nullptr;
     SessionID sessionID = 0;
@@ -69,7 +70,8 @@
             case cipher::rakp_auth::Algorithms::RAKP_HMAC_SHA1:
             {
                 session->setAuthAlgo(
-                        std::make_unique<cipher::rakp_auth::AlgoSHA1>(intAlgo));
+                        std::make_unique<cipher::rakp_auth::AlgoSHA1>(intAlgo,
+                        cryptAlgo));
                 break;
             }
             default: