[jira] [Resolved] (FC-315) Switch to make remote config optional

["Shawn McKinney (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FC-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shawn McKinney resolved FC-315.
-------------------------------
    Resolution: Fixed

> Switch to make remote config optional
> -------------------------------------
>
>                 Key: FC-315
>                 URL: https://issues.apache.org/jira/browse/FC-315
>             Project: FORTRESS
>          Issue Type: Improvement
>    Affects Versions: 2.0.8
>            Reporter: Shawn McKinney
>            Assignee: Shawn McKinney
>            Priority: Minor
>             Fix For: 3.0.0
>
>
> Currently, fortress config subsystem always reads a remote config entry during initialization. Sometimes instances don't need remote configuration storage which makes this an extraneous call.  Usually, it doesn't cause a problem as it will quiet fail the read if the config node isn't found.
> This is confusing at best, inefficient at possibly can cause problems for certain fortress extensions.
> To remedy, add a switch using an existing param:
> ```fortress.properties
> # This property is required and must be valid DN (format) but isn't always used:
> config.root=ou=NotUsed,o=empty
> ```
> Instead make this an optional property. When not found, the remote config step will be skipped altogether:
> ```Config.java
> if ( Config.getInstance().getProperty( GlobalIds.CONFIG_ROOT_PARAM ) == null )
> {
>      // perhaps this should be a warning:
>       LOG.info( "Remote config not enabled" );
>       return;
> }
> ```



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org