https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/AAA-204 aaa <p>This is essentially a rehash of aaa-password-service in <a href="https://jira.opendaylight.org/browse/AAA-203" title="Eliminate bleuprint from aaa-password-service" class="issue-link" data-issue-key="AAA-203"><del>AAA-203</del></a>, we need to convert this the hard way. Unless this blocks something it is low-priority.</p> AAA-204

Eliminate blueprint from aaa-encrypt-service

Task Medium Resolved Done Robert Varga Robert Varga pt Tue, 3 Nov 2020 21:30:37 +0000 Mon, 27 Mar 2023 07:51:04 +0000 Thu, 16 Feb 2023 10:39:14 +0000 0.17.6 General 0 2 <p>So I think this is problematic, because AAAEncryptionService is used by NETCONF to encrypt things in the datastore. Most notably we need a way to decrypt things as well.</p> <p>That means the configuration is coupled with datastore content, which unfortunately, is a very loose coupling.</p> <p>I think we need to retain the config datastore integration and do the heavy lifting through <font color="#000000">org.osgi.service.component.ComponentFactory</font>, meaning register a ClusteredDataTreeChangeListener on component startup and activate a service configuration. We already do this (without datastore, but reacting to OSGi SR) in <a href="https://github.com/opendaylight/mdsal/blob/00a6187de2248f3a44e1fe5b970269ff311dd5da/binding/mdsal-binding-runtime-osgi/src/main/java/org/opendaylight/mdsal/binding/runtime/osgi/impl/OSGiBindingRuntimeContextImpl.java" class="external-link" target="_blank" rel="nofollow noopener">mdsal-binding-runtime-osgi</a>).</p> <p> </p> <p>Looking at this a bit more, there is a lot going on here and it is intrinsically tied to the blueprint plugin re. the actual configuration:</p> <ul> <li>we rely on blueprint to populate the configuration, but then</li> <li>examine it and potentially generate password details, except</li> <li>all of that is not used, as we hard-code stuff at compile-time</li> </ul> <p>Let's split the effort up. As a first step, we will separate out configuration update concerns into a separate class wired through Blueprint (for now) and let AAAEncryptionServiceImpl pick up its configuration from OSGi SR and instantiate with OSGi DS. This will lead to an OSGi DS component being dependent on Blueprint, which is kind of okay and unblocks upstreams.</p> <p>The second part is to re-wire the configuration template/update wiring to work without blueprint and without initial config file.</p> Issue split AAA-250 Relates AAA-258 Development Epic Link AAA-202 Rank 0|i03vvz: