F-TICKS addition

[Chris Phillips]

Thanks Scott,

I've done a pass on this and added a comment or two into the ticket:
- idp.properties is the file for the settings NOT idp.ini (my bad in the
original write up & apologies for that)
- clarification on the placement of the hashed user map item in the
various extractor maps is desired
--  may trigger a multivalued state for an expected single value attribute
(see ticket for more detail:
https://issues.shibboleth.net/jira/browse/IDP-840 )


Is it safe for to presume that:
- These new values will be recognized by the Shib installer if provided on
the command line like any other -Didp.* property?
- That the settings are portable in this manner across both windows and
non windows installations?

A generic question about invoking the Shibboleth installer:
Does the installer filter any -Didp.* property or can anything be passed
in and then expected to be placed into the idp.properties file?

Thanks!

C

On 2015-11-05, 3:40 PM, "dev on behalf of Cantor, Scott"
<dev-bounces at shibboleth.net on behalf of cantor.2 at osu.edu> wrote:

>Per IDP-840, I've done what I think is feasible for this release without
>getting deeply into installer modifications we don't have time for. I
>think this is pretty reasonable considering the short time window.
>
>One enhancement to the contributed patch was to block it from reporting
>hashed usernames without a salt provided. That prevents us from having to
>supply a fixed salt people won't change.
>
>Default logging is to a file, but syslog is there, just commented out. I
>expect custom installers to be supplying a custom logback.xml anyway.
>
>If there's something more you think is needed *now*, speak up.
>
>-- Scott
>
>-- 
>To unsubscribe from this list send an email to
>dev-unsubscribe at shibboleth.net