15.2    Authorization and Consent
  • Security
  • 15.0 Security in Smile CDR
  • 15.1 Authentication Protocols
  • 15.2 Authorization and Consent
  • 15.3 Inbound Security Module
  • 15.4 Local Inbound Security Module
  • 15.5 LDAP Inbound Security Module
  • 15.6 Scripted Inbound Security Module
  • 15.7 SAML Inbound Security Module
  • 15.8 Trusted Client Mode
  • 15.9 Roles and Permissions
  • 15.10 Callback Scripts
  • 15.11 Anonymous Access
  • 15.12 Consent Service
  • 15.13 Consent Service: JavaScript API
  • 15.14 Consent Service: Java API
  • 15.15 Security Recipes
  • 15.16 Two Factor Authentication
  • 15.17 Troubleshooting Security
    • 15.4    Local Inbound Security Module   
       Table of Contents

    Inbound Security Module

    15.3.1Inbound Security Module

     

    An Inbound Security module is used to authenticate requests as they arrive. This includes any incoming FHIR requests, administrative commands on the JSON Admin API, and users logging into the Web Admin Console and the OpenID Connect login identity server.

    Various modules may depend on an Inbound Security module, and you can choose an appropriate type of Inbound Security module depending on your requirements. For example, the Local Inbound Security module stores credentials in a local table inside Smile CDR's own database. Other module types can store credentials in other places.

    Whether or not authentication credentials are being stored in Smile CDR's database, a local entry in Smile CDR's user table is always created for any user accessing the system. This is done in order to tie requests to audit log entries, etc.

    Security Overview

    15.3.2Permissions

     

    The Inbound Security module is responsible for accepting incoming credentials and validating them, as well as assigning a set of permissions to the user (or their current session).

    The Roles and Permissions page has information about the various permissions that can potentially be granted. The mechanism for granting them varies depending on the type of security module.

    15.3.3Callback Script

     

    A callback script may be executed during the authentication process in order to add additional functionality (e.g. by adding user attributes, by querying an existing system, by modifying the user permissions assigned to the session or by overriding userName of an external user).

    See onAuthenticateSuccess, getUserName for information on how to configure this.

       15.2    Authorization and Consent
  • Security
  • 15.0 Security in Smile CDR
  • 15.1 Authentication Protocols
  • 15.2 Authorization and Consent
  • 15.3 Inbound Security Module
  • 15.4 Local Inbound Security Module
  • 15.5 LDAP Inbound Security Module
  • 15.6 Scripted Inbound Security Module
  • 15.7 SAML Inbound Security Module
  • 15.8 Trusted Client Mode
  • 15.9 Roles and Permissions
  • 15.10 Callback Scripts
  • 15.11 Anonymous Access
  • 15.12 Consent Service
  • 15.13 Consent Service: JavaScript API
  • 15.14 Consent Service: Java API
  • 15.15 Security Recipes
  • 15.16 Two Factor Authentication
  • 15.17 Troubleshooting Security
    • 15.4    Local Inbound Security Module