- Symmetric Key Cryptography Using Random Key Generator Pdf File
- Symmetric Key Cryptography Using Random Key Generator Pdf Download
- Symmetric Key Cryptography Using Random Key Generator Pdf File

A **symmetric key** is a secret that encrypts and decrypts a message in symmetric-key cryptography.

In Azure Active Directory (Azure AD), when you create a service principal object to represent an application, the process also generates a 256-bit symmetric key to verify the application. This symmetric key is valid for one year by default.

The following steps show how to renew the symmetric key.

## Prerequisites

In 5 DES is improved using random number generator. Here message is divided into 64 bits blocks and different keys are generated using 56 bits master key. Keys generation is done using random number generator. Keys generated from 56 bits master are also 56 bits. For every block of message bits different key.

- Azure Active Directory (Azure AD) PowerShell module must be installed as directed in the Azure AD Powershell Reference.

## Renewing the symmetric key after expiry

You don't have to create a new service principal when the symmetric key associated with your application has expired. Instead, you can use the PowerShell commandlets provided by Microsoft Online Services (MSol) to issue a new symmetric key for an existing service principal.

## Symmetric Key Cryptography Using Random Key Generator Pdf File

To illustrate this process, let's assume you have already created a new service principal using the `New-MsolServicePrincipal`

command.

The creation process creates a symmetric key and an **AppPrincipalId** as shown.

## Symmetric Key Cryptography Using Random Key Generator Pdf Download

This symmetric key expires on 3/22/2018 at 3:27:53PM. To use the service principal beyond this time, you need to renew the symmetric key. To do so, use the `New-MsolServicePrincipalCredential`

command.

This creates a new symmetric key for the specified **AppPrincipalId**.

You can use the `GetMsolServicePrincipalCredential`

command to verify that the new symmetric key is associated with the correct service principal as shown. Notice that the command lists all keys that currently associated with the service principal.

Once you have verified that the symmetric key is indeed associated with the right service principal, you can update the service principal's authentication parameters with the new key.

You can then remove the old symmetric key using the `Remove-MsolServicePrincipalCredential`

command and verify that the key is removed using the `Get-MsolServicePrincipalCredential`

command.