Created You should publish the Web applications should be published in App Manager for users you create in App Manager as described below, to start using them.
Table of Contents maxLevel 3
Excerpt |
---|
Introduction to application approval processThe application (app) approval process involves all the states in an application life cycle from creation to retirement. |
...
Your actions are restricted based on the permissions that |
...
are assigned to |
...
you. The following topics illustrate the application approval process |
...
. Application approval process action definitions |
...
You can carry out the following actions in the application approval process |
...
.
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
Application approval process based on user rolesThe transitions in the app approval process, together with the permissions needed at each state are listed as follows:
Promoting web application to published stateAfter adding the |
...
application to the publisher, you need to promote its lifecycle state to published state, to publish it as follows. Once |
...
an application is added to App Manager, it is added to the registry as an asset, and a lifecycle is attached to the |
...
application. The lifecycle state for a newly created |
...
application |
...
is |
...
You can change the state |
...
to |
...
which will automatically initialize |
...
a work flow event. Once an admin user approves the work flow event, then lifecycle state moves to |
...
the |
...
state and will appear in the |
...
Store for |
...
you to consume. This behavior can be extended according to the user requirement with |
...
the provided extension points. Once |
...
an application reaches |
...
the |
...
state, an API resource will be created |
...
under |
...
directory. Name of the file will |
...
be |
...
|
...
|
After promoting the lifecycle state of the added web application, you need to configure security for it. For information on configuring security for web Web applications, see Securing with SAML2 SSO.