Nexeed
    • Introduction
    • User manual
      • Basic operation
      • Getting started
      • User
      • Groups
      • Roles
      • Organizations
      • Contracts
      • Modules
      • Identity providers
        • General Settings for the Identity Provider
        • Mapper Overview
      • Reports
      • Activity log
      • My Account
        • Overview: Login Tab
      • Configuration
        • Contents of the configuration file
        • How to work with the configuration file
    • Operations manual
      • Overview
      • System Architecture and Interfaces
      • System Requirements
        • macma/macma-webapp-backend
        • macma/macma-core
        • macma/macma-keycloak-mssql
      • Migration from Previous Versions
        • Migration to 1.37+
        • Migration to 1.34+
        • Migration to 1.33+
        • Migration to 1.32+
        • Migration to 1.31+
        • Migration to 1.29+
        • Migration to 1.28+
        • Migration to 1.27+
        • Migration to 1.26+
        • Migration to 1.25+
        • Migration to 1.21+
        • Migration to 1.20+
        • Migration to 1.19+
        • Migration to 1.18+
        • Migration to 1.17+
        • Migration to 1.16.0
        • Migration to 1.15.0
      • Setup and Configuration
        • Helm Configuration
        • macma/macma-core Configuration
        • macma/macma-keycloak-mssql Configuration
        • macma/macma-webapp-backend Configuration
        • Installation guide
        • Identity provider integration
        • Optional Configuration
        • Recommendations
        • Module Health Verification Endpoints and K8S Probes
      • Start and Shutdown
      • Regular Operations
        • Registering a new application in MACMA
          • Allowing application to use other applications
        • Change client secret of an application
      • Logging and Monitoring
        • Required Monitoring
        • Security Logging
          • Macma Security Events
          • Keycloak Security Events
          • Security Logging Format
        • Activity Logging
          • Activity Log Events
      • Known Limitations
        • Performance
        • General
        • Allowed characters and Internationalization
    • Developer documentation
      • Concepts
        • Authentication
        • Authorization
        • Resources
        • Roles
        • Sharing
      • Getting started
        • Registration
        • Authentication
        • Authorization
        • Multitenancy
      • How-to
        • Get & handle tokens
        • OAuth 2.0 for Mobile and Native Apps
        • Evolve authorization in your application lifecycle
        • Use Web Core for user login
        • Handle our integration events
        • Frequent How-To Questions for Application Developers
        • Do automated testing
        • Advertise things to colleagues
        • Integrate with additional environments
      • Deep dives
        • OAuth2 and its flows
        • OpenID Connect endpoints
    • Troubleshooting
      • Startup and availability
      • Identity provider integration
      • Resource deletion
      • Authentication
      • Authorization
    • API documentation
      • HTTP API
      • Event API
    • Glossary
Multitenant Access Control
  • Industrial Application System
  • Core Services
    • Block Management
    • Deviation Processor
    • ID Builder
    • Multitenant Access Control
    • Notification Service
    • Ticket Management
    • Web Portal
  • Shopfloor Management
    • Andon Live
    • Global Production Overview
    • KPI Reporting
    • Operational Routines
    • Shift Book
    • Shopfloor Management Administration
  • Product & Quality
    • Product Setup Management
    • Part Traceability
    • Process Quality
    • Setup Specs
  • Execution
    • Line Control
    • Material Management
    • Order Management
    • Packaging Control
    • Rework Control
  • Intralogistics
    • AGV Control Center
    • Stock Management
    • Transport Management
  • Machine & Equipment
    • Condition Monitoring
    • Device Portal
    • Maintenance Management
    • Tool Management
  • Enterprise & Shopfloor Integration
    • Archiving Bridge
    • Data Publisher
    • Direct Data Link
    • Engineering UI
    • ERP Connectivity
    • Gateway
    • Information Router
    • Master Data Management
    • Orchestrator

Nexeed Learning Portal

  • Multitenant Access Control
  • Operations manual
  • Setup and Configuration
  • Optional Configuration
1.37.1 1.37.0

Optional Configuration

Monitoring

MACMA logs on std:out. Monitoring solutions as e.g. the ELK stack can be attached.

SMTP

Via the Keycloak Admin UI it is possible to configure an SMTP server. Login to Keycloak Admin UI and configure for the particular tenant the SMTP setup via Realm Settings → Email.

Keycloak guide: https://www.keycloak.org/docs/latest/server_admin/#_email

Internationalization

It is possible to configure internationalization for the Keycloak identity provider via the Keycloak admin UI: switch on the Theme tab you can choose which locales you want to support and what the default locale will be. By default, the browser language is used.

Keycloak guide: https://www.keycloak.org/docs/latest/server_admin/#_themes

Footer Configuration

For customer hosted environments the footer is in the responsibility of the customer. The current default configuration does not offer any legal guidance. The default configuration is an example to explain how the configuration works. These links can be configured using environment variables.

Links

The links are indexed starting with 0. Up to 10 links can be defined. Two environment variables, one for the title and one for the URL, are required to define a link.

MACMA_FOOTER_LINKS_<index>_TITLE MACMA_FOOTER_LINKS_<index>_URL

Example 1. Example for the links

MACMA_FOOTER_LINKS_0_TITLE=First Label MACMA_FOOTER_LINKS_0_URL=https://example.com

MACMA_FOOTER_LINKS_1_TITLE=Second Label MACMA_FOOTER_LINKS_1_URL=/example.html

Further environment variables can be defined to localize the links. The localizations are indexed starting with 0. For every link up to 10 localizations can be defined. The language of each localization must be defined, the title and URL are optional. Therefore, it is possible as well to only localize the title or the URL.

Example 2. Example for the first localization for the first link

MACMA_FOOTER_LINKS_0_LOCALIZATIONS_0_LANGUAGE=de MACMA_FOOTER_LINKS_0_LOCALIZATIONS_0_TITLE=Erste Beschriftung MACMA_FOOTER_LINKS_0_LOCALIZATIONS_0_URL=https://example.de

Copyright

The footer shows a copyright statement. This copyright statement can be configured by environment variables as well.

Example 3. Copyright text configuration

MACMA_FOOTER_COPYRIGHTTEXT=Robert Bosch Manufacturing Solutions GmbH 2019-2020, all rights reserved

Localization is possible as well for example in German:

Example 4. Copyright text localization

MACMA_FOOTER_LOCALIZATIONS_0_LANGUAGE=de MACMA_FOOTER_LOCALIZATIONS_0_COPYRIGHTTEXT=Robert Bosch Manufacturing Solutions GmbH 2019-2020, alle Rechte vorbehalten.

The localizations are indexed starting by 0.

Cookie Banner / Privacy Settings

For customer hosted environments the cookie banner / privacy settings are in the responsibility of the customer. The current default configuration does not offer any legal guidance. The default configuration is an example to explain how the configuration works. These links can be configured using environment variables. For Docker Compose based deployment, the env-file application-macma-footer-config.env is offered to configure the cookie banner / privacy settings in addition to the footer.

To enable, set the environment variable MACMA_FOOTER_SHOWPRIVACYSETTINGS to true. Note, that the footer must be enabled for the privacy settings to be accessible. To enable the marketing consent option in the MACMA cookie banner, the environment variable NEXEED_MACMA_FOOTER_PRIVACYSETTINGS_ENABLEMARKETINGCONSENT can be set to true.

Footer link text

The footer shows a copyright statement. This copyright statement can be configured by environment variables as well.

Example 5. Copyright text configuration

MACMA_FOOTER_PRIVACYSETTINGSTEXT=Privacy settings

Localization is possible as well for example in German:

  1. Copyright text localization

MACMA_FOOTER_LOCALIZATIONS_0_LANGUAGE=de MACMA_FOOTER_LOCALIZATIONS_0_PRIVACYSETTINGSTEXT=Privatsphäreeinstellungen

The localizations are indexed starting by 0.

Contents

The contents of the cookie banner and privacy settings can be configured as well. The following options are available:

Example 6. Example for the links

MACMA_FOOTER_PRIVACYSETTINGS_COMFORTCOOKIELINK=page1.html MACMA_FOOTER_PRIVACYSETTINGS_MARKETINGCOOKIELINK=/page2.html MACMA_FOOTER_PRIVACYSETTINGS_DATAPROTECTIONINFOLINK=page3.html MACMA_FOOTER_PRIVACYSETTINGS_CORPORATEINFORMATIONLINK=/page4.html

These links can be relative or absolute and may contain complete URLs like https://bosch.com as well.

Further environment variables can be defined for localization. The localizations are indexed starting with 0. Up to 10 localizations can be defined. The language of each localization must be defined, the specific properties are optional. Therefore, it is possible as well to only localize specific properties like a single link.

Example 7. Example for the first localization for the first link

MACMA_FOOTER_PRIVACYSETTINGS_LOCALIZATIONS_0_LANGUAGE=de MACMA_FOOTER_PRIVACYSETTINGS_LOCALIZATIONS_0_COMFORTCOOKIELINK=page1-de.html MACMA_FOOTER_PRIVACYSETTINGS_LOCALIZATIONS_0_MARKETINGCOOKIELINK=/page2-de.html

Again, these links can be relative or absolute and may contain complete URLs like https://bosch.com as well.

Contents

© Robert Bosch Manufacturing Solutions GmbH 2023-2025, all rights reserved

Changelog Corporate information Legal notice Data protection notice Third party licenses