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
  • Overview
  • Example

Was this helpful?

Edit on GitHub
  1. Developer Reference
  2. RealmJoin API

Authentication

Last updated 10 months ago

Was this helpful?

Overview

The RealmJoin backend expects application credentials (username and secret) presented via .

Username and secret will be created for you by our RealmJoin operations team. Please feel free to reach out if you want to integrate RealmJoin into your own tools and processes!

Example

For the sake of demonstration, let us assume the username created for you is t-12341234and the secret is myS3cret!.

To authenticate, concatenate username and password, separated by a colon (t-12341234:myS3cret!)and encode this into a Base64-String.

Our example username and secret will encode to dC0xMjM0MTIzNDpteVMzY3JldCE=

Now, on every request against the RealmJoins backend service present an http header with the resulting Authorization:

Authorization: Basic dC0xMjM0MTIzNDpteVMzY3JldCE=

RealmJoin will then allow you to interact with ressources in your envorinment. It will not allow yuo to interact with resources foreign to your tenant. Remember that RealmJoin Portal requires SSL/TLS transport layer encryption on every request - your credentials will not be exposed to the traversing networks.

http basic authentication