# User Guide

## IAM Authentication modules

When the IAM Authentication modules are deployed and properly configured the user interface change in few component. The login portlet will include, among the other enabled protocols, the new *INDIGO AAI* authentication method, as shown in the following picture:

![Login portlet with INDIGO AAI authentication](/files/-LFRpCcDzDeERcGXsUsM)

If a user clicks on *INDIGO AAI* a pop-up window is created with the IAM login page. After the login the pop-up page is automatically closed and the user is authenticated in the portal.

When a new user try to access the portal, he/she has to provide the consensus to release the tokens to the Liferay based portal. This request is performed twice: once for the access token and the other for the refresh token. Following authentications will not require the user consensus. This will be requested again if different scopes are requested.

Finally, the user can verify the tokens released by IAM going to his/her personal account page. In the *My Account* page, under the tab *Miscellaneous* there are the *Custom Fields* attributes. IAM tokens nad user subject are among the custom fields as shown in the following picture:

![INDIGO AAI tokens](/files/-LFRpCcGry4C5F5LniWI)

## FutureGateway administration modules

The FutureGateway administration modules add a new panel in the control panel of Liferay at `Liferay > Control Panel > Apps > FutureGateway` which is visible to the enabled user (a special role is requested to access the panel).

The panel presents a multi tab interface with three tabs for the main resources of the FutureGateway: *tasks*, *applications* and *infrastructures*. In each tab a table with the available resources is shown, as shown in the following figure:

![FG applications](/files/-LFRpCcW6dtPW2f7pbkx)

User can look at the resource details by clicking the id. This will open a modal window with an information tree containing all the resource details and a button to delete the resource, although the user should be enabled in the FutureGateway to delete the resources. The modal windows is shown in the following figure:

![FG application details](/files/-LFRpCcYI1z1-rdegP8_)

Finally, in the right bottom of the applications and infrastructures tab a button with a `+` sign open an insert page where the user can add a new resource. The button will open a new page with a form, depending on the resource type, containing all the possible fields.

## FutureGateway customisable application module

Customisable application portlet provides direct access to selected applications and allows the user to list all submitted tasks and check their status. To submit new tasks it is needed only to fill all required fields in a *submission panel* and confirm it by pressing *Submit* button. ![Customisable Portlet](/files/-LFRpCc_XE5lZHiCv1Mm)

## Kepler Status Portlet

The portlet works only with users logged in using IAM authentication method. ![You must be logged in](/files/-LFRpCcbjdyaHFmK8-IA)

Once logged, user is prompted to provide name of the application. ![Application name](/files/-LFRpCcdIdQCjjQp01-G)

Given invalid name, portlet presents a meaningful error message. ![Error message](/files/-LFRpCcf__xUEIrc5_H-)

When the application is found, portlet will begin to query for all tasks of the current user which are of the application type. ![Application query](/files/-LFRpCchvpGk55O8svW7)

The results are shown in a table. An icon distinguishing `DONE`, `ABORTED` and `RUNNING` tasks is shown next to the task's id and description. Rows of the table can be clicked to extend a panel with runtime data of the selected tasks. ![Runtime data](/files/-LFRpCcjWYMHs1-Smwvn)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://indigo-dc.gitbook.io/liferay-plugins/user.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.