medcrypt::guardian::AuthenticationManager

Container for authentication restrictions.

#include <AuthenticationManager.h>

Public functions

Name
~AuthenticationManager()	This is the destructor.
GetRestrictions(std::list< AuthenticationDomain > * out_restrictions_by_domain)	This gets all restrictions.
GetRestrictionByService(const char in_service_name, AuthenticationDomain out_restriction)	This gets all restrictions by service.

function ~AuthenticationManager

~AuthenticationManager()

The destructor.

Parameters:

• none

Return: none

The destructor does no work.

function GetRestrictions

Status GetRestrictions(
    std::list< AuthenticationDomain > * out_restrictions_by_domain
)

Get all restrictions.

Parameters:

• out_restrictions_by_domain list of domains and their restrictions,

Returns:

• OK out_restrictions_by_domain is populated with restrictions

• FAIL general failure, out_restrictions_by_domain is unmodified

• BADPARAM out_restrictions_by_domain is nullptr

Return: medcrypt::guardian::Status

Returns a list of all AuthenticationRestrictions in the system.

function GetRestrictionByService

Status GetRestrictionByService(
    const char * in_service_name,
    AuthenticationDomain * out_restriction
)

Get restrictions by service.

Parameters:

• in_service_name null terminated string of service name

• out_restriction restriction set for in_service_name

Returns:

• OK out_restriction is populated with restrictions for in_service_name

• FAIL general failure, out_restriction is unmodified

• BADPARAM in_service_name is nullptr or empty, or out_restriction is nullptr

• MISCONFIGURED in_service_name cannot be found or is not configured to share restrictions

Return: medcrypt::guardian::Status

Returns a single AuthenticationRestriction for the specified service name

Debugging and logging

Guardian does not create log files. Instead, logging is controlled by the application:

• Guardian logs to stdout and stderr, which appear in the terminal/CLI of the running application during execution. Look for specific error codes or connection failures in the output.

• Custom logging: Use SetLoggingCallback to redirect log messages to a callback function, stopping terminal output and allowing custom log handling

• Log control: Applications can control log level and verbosity.

• Guardian Cloud UI: Check the Guardian Cloud interface for additional error details and provisioning status.