You also define in some way at which **moments** your app will send those requests or events.

And **your users** define in some way (for example in a web dashboard somewhere) the **URL** where your app should send those requests.

			<li class="nav-header"><la:message key="labels.sidebar.menu" /></li>
			<c:if test="${fe:permission('admin-dashboard-view')}">
				<li class="nav-item">
					<a class="nav-link <c:if test="${param.menuCategoryType=='dashboard'}">active</c:if>" <c:if test="${param.menuCategoryType=='dashboard'}">aria-current="page"</c:if>
					   href="${fe:url('/admin/dashboard/')}">
						<i class="nav-icon fa fa-tachometer-alt" aria-hidden="true"></i>

def new_subscription(body: Subscription):
    """
    When a new user subscribes to your service we'll send you a POST request with this
    data to the URL that you register for the event `new-subscription` in the dashboard.
    """


@app.get("/users/")
def read_users():

      label: Anything else we need to know?

  - type: textarea
    id: sigs
    attributes:
      label: Relevant SIG(s)
      description: You can identify the SIG from the "prowjob_config_url" on the testgrid dashboard for a test.

 * governing permissions and limitations under the License.
 */
package org.codelibs.fess.app.web.base;

import org.codelibs.fess.app.web.admin.AdminAction;
import org.codelibs.fess.app.web.admin.dashboard.AdminDashboardAction;
import org.codelibs.fess.mylasta.action.FessUserBean;
import org.lastaflute.web.response.HtmlResponse;

/**
 * Abstract base action class for handling login functionality in Fess.

#   are all settings for the scripts. TF's CI jobs are all made of a combination
#   of these env files.
#
#   If you've clicked on a test result from our CI (via a dashboard or GitHub link),
#   click to "Invocation Details" and find BUILD_CONFIG, which will contain a TFCI
#   value in the "env_vars" list that you can choose to copy that environment.

import okio.ByteString;

/**
 * API access to the <a href="https://api.slack.com/apps">Slack API</a> as an application. One
 * instance of this class may operate without a user, or on behalf of many users. Use the Slack API
 * dashboard to create a client ID and secret for this application.
 *
 * <p>You must configure your Slack API OAuth and Permissions page with a localhost URL like {@code

w\":24,\"h\":15,\"i\":\"6\"},\"version\":\"7.2.0\",\"panelIndex\":\"6\",\"embeddableConfig\":{},\"panelRefName\":\"panel_5\"}]","timeRestore":false,"title":"fess_log","version":1},"id":"cec1a520-b2b6-11e9-b23e-033a71496733","migrationVersion":{"dashboard":"7.0.0"},"references":[{"id":"87b6d8d0-b2b6-11e9-b23e-033a71496733","name":"panel_0","type":"visualization"},{"id":"1523d560-b2b7-11e9-b23e-033a71496733","name":"panel_1","type":"visualization"},{"id":"a9a84830-b2ba-11e9-b23e-033a71496733","nam...

    @Test
    public void test_doFilter_adminPathExcluded() throws IOException, ServletException {
        setConfig(10, 10);
        testableFilter.setCpuPercent((short) 99);
        mockRequest.setRequestURI("/admin/dashboard/");

        testableFilter.doFilter(mockRequest, mockResponse, mockFilterChain);

        assertTrue(mockFilterChain.wasDoFilterCalled());
    }

    @Test

    <name>permission</name>
    <function-class>org.codelibs.fess.taglib.FessFunctions</function-class>
    <function-signature>boolean hasActionRole(java.lang.String)</function-signature>
    <example>${fe:permission("admin-dashboard")}</example>
  </function>