LogoLogo
LogoLogo
  • Welcome
    • Navigation
  • RealmJoin Deployment
    • Onboarding
    • Required Permissions
    • Infrastructure Considerations
      • Multi User Devices
    • Migration to RealmJoin vNext
  • User, Group and Device Management
    • Overview
    • User Profile
    • Organization Details
    • User, Group and Device Lists
      • Advanced Search
      • User Details
      • Group Details
      • Device Details
    • User and Group Settings
      • Available RealmJoin Policies
  • App Management
    • Packages
      • Package Store
        • Application Store Details
      • Package Management
      • Package Details
      • Package Assignments
        • Package Migration
      • Package Settings
      • Packaging Requests
        • Organic Packages
    • AVD Templates
  • Automation
    • Connecting Azure Automation
      • Required Permissions
      • Runbook Parameters
    • Runbooks
      • Runbook Customization
      • Runbook Permissions
      • Naming Conventions
      • Runbook Scheduling
      • Runbook Logs
        • Runbook Job Details
      • Runbooks Changelog
    • Requirements
    • Remediation Scripts
  • RealmJoin Agent
    • Features
      • Local Admin Password Solution (LAPS)
        • KeyVault
        • Application Insights
      • Notifications
      • AnyDesk Integration
        • AnyDesk configuration
      • App Deployment using the Agent
        • RealmJoin ESP
    • Deploying the Agent
    • User Interface
  • Logs
    • Connecting Azure Log Analytics Workspace
    • Audit Log
  • RealmJoin Settings
    • Overview
    • General
    • Roles and Permissions
      • Pre-defined Roles
      • Custom Roles
        • Available Permissions
    • Group Namespaces
    • Workplace Cloud Storage
    • Self Service Forms
  • Developer Reference
    • RealmJoin API
      • Authentication
    • Interacting with Runbooks
    • Simulating a Runbook Environment
    • Local Admin Password Management
  • Other
    • FAQ
      • Security
    • Troubleshooting
      • Package Installation Issues
        • Collecting Logfiles
        • Logfiles Structure
        • Analysing chocolatey.log
        • Troubleshooting failed chocolatey packages
        • Troubleshooting failed craft packages
        • Fixes for common issues
        • Intunewin Debugging
      • LAPS Issues
        • LAPS account passwords cannot be retrieved
        • Requested LAPS Accounts are not being created
    • Changelog
  • Legal
    • Licensing
    • Support
  • RealmJoin Website
Powered by GitBook
On this page
  • Create KeyVault
  • KeyVault Storage of Secrets

Was this helpful?

Edit on GitHub
  1. RealmJoin Agent
  2. Features
  3. Local Admin Password Solution (LAPS)

KeyVault

Cloud applications and services use cryptographic keys and secrets to help keep information secure. Azure Key Vault safeguards these keys and secrets. When you use Key Vault, you can encrypt authentication keys, storage account keys, data encryption keys, .pfx files, and passwords by using keys that are protected by hardware security modules.

Create KeyVault

The following table shows the steps for the creation of Azure KeyVault and the configuration of Access Policy for RealmJoin LAPS:

Task
Image

2. Start with Create a resource

3. Type in Key Vault in the search field

4. On the detail page click Create

5. Fill out the required fields on the Basic Tab. Please make sure to use a distinct naming scheme for the KeyVault URL. For example: rj-[tenant]-[service]

Note: This is a DNS name, so global unique Press Next.

6. Access configuration Please choose "Vault access policy" for Permission model.

7. Create an Access Policy for RealmJoin Press Create and choose "Key, Secret & Certificate Management" as template. Additional add "Select all" for Cryptographic Operations. Press Next.

8. Add "RealmJoin" as Principal Press Next.

9. Click Create

10. Review your settings and configurations and click Review + Create

11. Wait for the successful deployment

12. Click Go to resource

KeyVault Storage of Secrets

RealmJoin will not store the secret in any proprietary storage but instead create an Azure KeyVault Secret to store it in a secure and auditable way. The KeyVault API is documented here:

The entry in KeyVault will be added with the Azure device ID as a key and the plain GUID as the secret value. See the following example:

Last updated 1 month ago

Was this helpful?

1. Open

13. Finally, go to Overview and share the DNS Name with the

https://docs.microsoft.com/en-us/rest/api/keyvault/secrets/set-secret/set-secret
Azure Portal
RealmJoin Support