Abstract: A computing system (100) that includes at least one microapp (202) and a container application (204) configured to receive an application output from the microapp(s) (202,602) via an application programming interface. The computing system (100) can include at least one processor (112,132) and at least one tangible, non-transitory computer-readable medium that stores instructions that, when executed by the at least one processor (112,132), cause the at least one processor (112,132) to perform operations. The operations can include providing, for display within a first panel (304) in a user interface (306), a navigation bar (302) based on data received from the container application (204); receiving, at the container application (204), the application output from the at least one microapp (202) via the application programming interface; and providing, for display within a second panel in the user interface (306), data describing the application output.

Abstract: Techniques described herein are directed to proxies configured to handle identity and access management for a web application. For instance, a first proxy receives requests to the application from a browser. The first proxy redirects the browser to an identity endpoint, which prompts the user to enter authentication credentials for the application. Upon successful authentication, the endpoint provides an access token for accessing web APIs to the first proxy. The first proxy provides the token to a second proxy, which stores the token. The second proxy receives anonymous API calls from the web application to the web APIs. When receiving an anonymous API call, the second proxy obtains the token and inserts it into an outgoing request to the API. Responsive to the API returning a message indicating that the token is invalid, the second proxy communicates with the first proxy to obtain a new token from the endpoint.

Abstract: A computing system (100) that includes at least one microapp (202) and a container application (204) configured to receive an application output from the microapp(s) (202,602) via an application programming interface. The computing system (100) can include at least one processor (112,132) and at least one tangible, non-transitory computer-readable medium that stores instructions that, when executed by the at least one processor (112,132), cause the at least one processor (112,132) to perform operations. The operations can include providing, for display within a first panel (304) in a user interface (306), a navigation bar (302) based on data received from the container application (204); receiving, at the container application (204), the application output from the at least one microapp (202) via the application programming interface; and providing, for display within a second panel in the user interface (306), data describing the application output.

Abstract: Techniques described herein are directed to proxies configured to handle identity and access management for a web application. For instance, a second proxy receives requests to the application from a browser. The second proxy redirects the browser to an identity endpoint, which prompts the user to enter authentication credentials for the application. Upon successful authentication, the endpoint provides an access token for accessing web APIs to the second proxy. The second proxy provides the token to a first proxy, which stores the token. The first proxy receives anonymous API calls from the web application to the web APIs. When receiving an anonymous API call, the first proxy obtains the token and inserts it into an outgoing request to the API. Responsive to the API returning a message indicating that the token is invalid, the first proxy communicates with the second proxy to obtain a new token from the endpoint.

Abstract: Techniques described herein are directed to proxies configured to handle identity and access management for a web application. For instance, a first proxy receives requests to the application from a browser. The first proxy redirects the browser to an identity endpoint, which prompts the user to enter authentication credentials for the application. Upon successful authentication, the endpoint provides an access token for accessing web APIs to the first proxy. The first proxy provides the token to a second proxy, which stores the token. The second proxy receives anonymous API calls from the web application to the web APIs. When receiving an anonymous API call, the second proxy obtains the token and inserts it into an outgoing request to the API. Responsive to the API returning a message indicating that the token is invalid, the second proxy communicates with the first proxy to obtain a new token from the endpoint.