===== Authentication =====

==== Platform access ====

Access to the PLORABUNT portal is provided through the centralized authentication system Keycloak, integrated with the D4Science infrastructure.

Users can authenticate using an already registered account or by relying on external Identity Providers.


https://plorabunt-itserr.d4science.org

By clicking on the *Access* button (located in the top-right area of the navigation bar), the user is redirected to the Keycloak login page. 
----
==== Login page ====

The authentication page includes the following elements:

**Main fields**
  * Username or email
  * Password
  * *Remember me* checkbox
  * *Forgot password?* link

**External authentication buttons**  
Users can log in using the following integrated academic or social providers:

  * Academic / Other
  * Google
  * LinkedIn
  * Twitter
  * GitHub
  * ORCID
  * CNR-ISTI

**Additional options**
  * *New user? Register* → allows the creation of a new D4Science account
  * *Terms of Use*, *Cookies Policy*, and *Privacy Policy* are available in the footer area of the page


{{plorabunt:plorabunt_keycloak.png?650|Keycloak}}
----
==== Roles and permissions after login ====

After successful authentication, the user is redirected to the platform homepage, where the top toolbar is updated with additional elements compared to the public view.

^ Element ^ Description ^
| **Add Resource** | Allows Researchers to create a new resource (item). |
| **Export** | Enables the export of search results in CSV or JSON format. |
| **User menu (profile icon)** | Provides access to the Dashboard and Logout options. |
| **Dashboard** | Accessible only to authenticated users; displays the requests created by the Researcher. |

Access to the restricted area is not mandatory for consultation purposes: the search functionality is also available to unauthenticated users.  
However, only users logged in with the **Researcher** or **WPLead** role are allowed to manage resources or export search results.

----
==== Logout ====

From the user menu (profile icon located in the top-right corner), selecting *Logout* terminates the active session and redirects the user back to the public view of the platform.

{{plorabunt:plorabunt_logout.png?300|Logout}}
----
==== Navigation and breadcrumb ====

After authentication, a navigation bar is displayed at the top of the interface, allowing users to orient themselves within the different sections of the platform.

{{ plorabunt:plorabunt_breadcrumb.png?700|Breadcrumb and Navigation }}

**Main navigation elements**


^ Element ^ Description ^
| **ITSERR logo** | Located in the top-left corner. It is clickable and always redirects to the PLORABUNT homepage. |
| **Breadcrumb** | Displays the current navigation path (e.g. *Home / Dashboard*) and allows quick access to previous levels. |
| **Right toolbar** | Includes the *Export* and *Add Resource* buttons, as well as the user profile icon. |


The breadcrumb is automatically updated during navigation and indicates the current section:

  * *Home / Search* for the main search page
  * *Home / Add Resource* for the creation of a new resource
  * *Home / Dashboard* for the personal user area

This structure ensures a consistent and simplified navigation experience across the entire application.

----
==== User roles ====

The platform defines three main user profiles, each with specific responsibilities and permissions.

^ Role ^ Description ^ Main permissions ^
| **Admin** | Technical user account employed by the management team for setup and maintenance operations. | Backend management, system maintenance, configuration of roles and permissions. |
| **WPLead** | User responsible for reviewing and validating requests submitted by Researchers. | Can approve, reject, delete, or view submitted requests. |
| **Researcher** | User enabled to create new resources (“items”) and manage their own submissions. | Can create, edit, submit, view, and delete their own requests. |

Requests submitted by Researchers are reviewed by the WPLead according to the following logic:

  * If approved, the resource is published in the central database.
  * If rejected, the resource is returned to Draft status, accompanied by a rejection motivation that allows the user to modify and resubmit the request.

This workflow ensures data quality and consistency before publication, while maintaining an efficient and collaborative validation process.