2 * ============LICENSE_START====================================================
4 * ===========================================================================
5 * Copyright (c) 2018 AT&T Intellectual Property. All rights reserved.
6 * ===========================================================================
7 * Licensed under the Apache License, Version 2.0 (the "License");
8 * you may not use this file except in compliance with the License.
9 * You may obtain a copy of the License at
11 * http://www.apache.org/licenses/LICENSE-2.0
13 * Unless required by applicable law or agreed to in writing, software
14 * distributed under the License is distributed on an "AS IS" BASIS,
15 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
16 * See the License for the specific language governing permissions and
17 * limitations under the License.
18 * ============LICENSE_END====================================================
27 * Similar to Java EE's Spec from Annotations 1.1, 2.8
29 * That Spec, however, was geared towards being able to route calls to Methods on Objects, and thus needed a more refined
30 * sense of permissions hierarchy. The same mechanism, however, can easily be achieved on single Servlet/Handlers in
31 * POJOs like Jetty by simply adding the Roles Allowed in a similar Annotation
34 package org.onap.aaf.cadi.filter;
35 import static java.lang.annotation.ElementType.TYPE;
36 import static java.lang.annotation.RetentionPolicy.RUNTIME;
38 import java.lang.annotation.Retention;
39 import java.lang.annotation.Target;
42 * JASPI Style Annotation of RolesAllowed when the coding style is desired but actually including all
43 * JEE jars is not. If using actual JASPI, use official @interface classes, not this one...
49 public @interface RolesAllowed {
51 * Security role of the implementation, which doesn't have to be an EJB or CORBA like object. Can be just a