---
title: "Additional Resources"
slug: "additional-resources"
updated: 2025-02-10T10:33:21Z
published: 2025-02-10T10:33:21Z
canonical: "help.iobeya.com/additional-resources"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.iobeya.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Additional Resources

## SAML logs on the iObeya server

As a Administrateur de plateforme, you can download the application logs from the administration interface (for support or maintenance purposes, for example):

![SSO - accessing logs](https://cdn.document360.io/e61a3dcb-bae0-4a4f-820c-85b0f6ef7f3c/Images/Documentation/SSO%20-%20accessing%20logs.png)

1. Select **Download logs** in the **Tools** section on the left-hand side menu of the administraiton interface.
2. Select **Ok**.

Logs are downloaded from the server into a ZIP file

These logs show you when people manage to log in, and also when they fail.

You should find, in the logs, for each AuthNRequest line, a AuthNResponse.

For example, when there is a success, you should find the email address in the response:

```accesslog
INFO [SAMLDefaultLogger] AuthNRequest;SUCCESS…
…
INFO [SAMLDefaultLogger] AuthNResponse;SUCCESS... jdoe@mycompany.com...
```

For example, when there is a failure:

```accesslog
INFO [SAMLDefaultLogger] AuthNRequest;SUCCESS...
...
INFO [SAMLDefaultLogger] AuthNResponse;FAILURE...
```

If the file does not exist in the logs, here is how to activate SAML debug information in the log files

On iObeya platform, **log4j2.xml** is usually located in the “settings” folder in the iObeya folder.

> [!NOTE]
> Note:
> 
> If you cannot find the file, go to the conf\Catalina\localhost folder in Tomcat, and open the .xml context file.
> 
> The **log4j2FilePath** gives you the path to the file.

Open that file and uncomment the following part, by deleting the “<!--” and “-->” highlighted in yellow

```accesslog
INFO [SAMLDefaultLogger] AuthNRequest;SUCCESS…
…
INFO [SAMLDefaultLogger] AuthNResponse;SUCCESS... jdoe@mycompany.com...
```

For example, when there is a failure:

```accesslog
<!-- DEBUG FILE LOG Console -->
<!--
 <RollingFile name="debugfile" fileName="/var/iobeya/logs/appDebug.log"            filePattern="/var/iobeya/logs/appDebug-%d{yyyy-MM-dd}-%i.log.gz">
  <PatternLayout>
   <Pattern>%d{yyyy-MM-dd HH:mm:ss} %5p [%c{1}] %m%n</Pattern>
  </PatternLayout>
  <Policies>
   <TimeBasedTriggeringPolicy />
   <SizeBasedTriggeringPolicy size="250 MB"/>
  </Policies>
  <DefaultRolloverStrategy max="5"/>
 </RollingFile>
-->
```

And add after <loggers>.

```accesslog
<!-- SAML -->
<Logger name="org.opensaml" level="DEBUG" />
<Logger name="org.springframework.security.saml" level="DEBUG" />
<Logger name="com.iobeya.auth.saml" value="DEBUG" />
<Logger name="org.springframework.security.web.authentication.SimpleUrlAuthenticationFailureHandler" value="DEBUG" />
```

## SAML tool

> [!TIP]
> Recommendation:
> 
> The use of [SAML tool](https://samltool.io/) is highly recommended to troubleshoot the setup of the SAML connexion (to be installed by a person who is supposed to test SSO connexion).
> 
> With it, you can see if there are attributes in the SAML response and the names of the attributes you need to complete the iObeya SAML configuration.

To use the SAML tool:

1. Open your platform.
2. Launch your browser’s Devtools.
3. Perform the action that initiates SAML login.
4. Find SSO from the Network panel and look for a network request with `SAMLResponse` in the Payload.

![SSO - SAML tool 1](https://cdn.document360.io/e61a3dcb-bae0-4a4f-820c-85b0f6ef7f3c/Images/Documentation/SSO - SAML tool 1(2).png)
5. Copy the `SAMLResponse` value.
6. Open the [SAML tool](https://samltool.io/) and paste the `SAMLResponse` value into the tool.

![SSO - SAML tool 2](https://cdn.document360.io/e61a3dcb-bae0-4a4f-820c-85b0f6ef7f3c/Images/Documentation/SSO%20-%20SAML%20tool%202.png)

View the extracted SAML information:

![SSO - SAML tool 3](https://cdn.document360.io/e61a3dcb-bae0-4a4f-820c-85b0f6ef7f3c/Images/Documentation/SSO%20-%20SAML%20tool%203.png)

## Embedding SSO login into the workflow of adding a user to a room

![SSO - embedding SSO login into the workflow](https://cdn.document360.io/e61a3dcb-bae0-4a4f-820c-85b0f6ef7f3c/Images/Documentation/SSO - embedding SSO login into the workflow(1).png)

Utilisateur ayant le plus haut niveau d'accès et de contrôle au sein de la plateforme. Ce rôle est responsable de la gestion de l'ensemble de la plateforme, incluant la configuration des réglages, la gestion des utilisateurs et des permissions, ainsi que l'organisation des salles et des domaines. L'administrateur de la plateforme veille à toutes les tâches administratives et maintient l'intégrité générale de l'instance iObeya de l'organisation.