Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I8781b368b3383e4ccc42cc9f034543273cbd5ca4
Issue-ID: POLICY-1580
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
|
|
It is generic with extended expiration, and support for
policy-distribution and policy-apex-pdp components.
Change-Id: Ibbaa6206a9aa6833296ae8707d2a816809d11077
Issue-ID: POLICY-1377
Signed-off-by: Jorge Hernandez <jorge.hernandez-herrero@att.com>
|
|
This allows to talk directly to OOM PDP-X pods
without going through the service.
Change-Id: I09bd5253a79142f6566806b97be4bb6c223826f4
Issue-ID: POLICY-1198
Signed-off-by: Jorge Hernandez <jorge.hernandez-herrero@att.com>
|
|
The keystore has been regenerated using the latest tooling
from AAF.
Previous versions seem to add a bogus " fqdn" which makes
the particular policy.api.simpledemo.onap.org invalid.
The latest version does not append it.
Change-Id: I96e4d272e8f0ab6eb84a12384645bf9a49dbbd09
Issue-ID: POLICY-1193
Signed-off-by: Jorge Hernandez <jh1730@att.com>
|
|
Some changes have been made since the first set of
stores were generated from the cert manager tooling
in the windriver test instance used for this purpose.
Change-Id: I976333df7e020bda76c5cbdc9c0be752e5a88778
Issue-ID: POLICY-1156
Signed-off-by: Jorge Hernandez <jh1730@att.com>
|
|
Added cadi properties and modified policy aaf client code.
Fixed issue with namespace and modified code to reverse it for
structuring the username sent in AAF API call
Added properties for keystore and keystore password after getting error
response from AAF when setting up the connection to AAF
Missed a fix for one of Jorge's comments in last patch, here it is.
Change-Id: Ic164ade8aa34da95a560c1592656e0caf990a595
Issue-ID: POLICY-913
Signed-off-by: Michael Mokry <mm117s@att.com>
|
|
Change-Id: I21ed7a0fea5ea7d62857a077fa2568da4af99d26
Issue-ID: POLICY-1057
Signed-off-by: Jorge Hernandez <jh1730@att.com>
|
|
OOM team reported issues with ONAP installation in
terms of config map sizes. After discussion with
OOM team, one solution is to cook it in the docker
image itself. This will solve the size issue on
the OOM side.
Change-Id: I2ca20bdc3aa8ee959c5e4c1d07483fe5f0c14607
Issue-ID: POLICY-747
Signed-off-by: Jorge Hernandez <jh1730@att.com>
|