configuration/environments/security-service-master
... ...
@@ -20,7 +20,7 @@ ADDITIONAL_JAVA_ARGS="$ADDITIONAL_JAVA_ARGS -Dsecurity.sharedAcrossSubdomainsOf=
20 20
#REPLICATE_MASTER_SERVLET_PORT=443
21 21
#REPLICATE_MASTER_EXCHANGE_NAME=security_service
22 22
# Activate SAP Branding
23
-ADDITIONAL_JAVA_ARGS="$ADDITIONAL_JAVA_ARGS -Dcom.sap.sse.debranding=false"
23
+ADDITIONAL_JAVA_ARGS="$ADDITIONAL_JAVA_ARGS -Dcom.sap.sse.branding=SAP"
24 24
25 25
# Provide authentication credentials for a user on security-service.sapsailing.com permitted to replicate, either by username/password...
26 26
#REPLICATE_MASTER_USERNAME=(user for replicator login on security-service.sapsailing.com server having SERVER:REPLICATE:<server-name> permission)
java/com.sap.sailing.www/release_notes_admin.html
... ...
@@ -32,6 +32,27 @@
32 32
and install <em>all</em> releases available. For the time being, and for simplicity,
33 33
we decided to not require a GitHub access token, which however will cause a rate limit
34 34
of 60 release requests per hour per IP address.</li>
35
+ <li>Branding is now configurable beyond just switching it on and off. The corresponding
36
+ VM argument / system property name has changed from <tt>com.sap.sse.debranding</tt>
37
+ with its possible values <tt>true</tt> and <tt>false</tt> to <tt>com.sap.sse.branding</tt>
38
+ which can either be left empty to deactivate branding altogether, matching the old
39
+ <tt>true</tt> configuration for de-branding the solution, which was also the default,
40
+ or you can specify the ID of an existing branding configuration, such as <tt>SAP</tt>.
41
+ The command line option for an active SAP branding hence would look like this:
42
+ <pre>
43
+ -Dcom.sap.sse.branding=SAP
44
+ </pre>
45
+ and this is to be used only in an SAP context according to SAP's branding rules.
46
+ See also <a href="https://brand.sap.com/">https://brand.sap.com/</a> and
47
+ <a href="https://wiki.sapsailing.com/wiki/info/landscape/branding-setup.md">our wiki entry on branding configurations</a>.
48
+ </li>
49
+ <li>The project Wiki can now be viewed publicly, in line with the publication of the underlying
50
+ Git repository, at <a href="https://wiki.sapsailing.com">https://wiki.sapsailing.com</a>.
51
+ Currently, write access has to be requested at <a href="mailto:support@sapsailing.com">support@sapsailing.com</a>,
52
+ but you may also create a <a href="https://github.com/SAP/sailing-analytics/pulls"></a>pull request</a>
53
+ for changes you'd like to see appear in the Wiki. We are working on granting committers
54
+ write-access through a GitHub OAuth app soon. See also
55
+ <a href="https://bugzilla.sapsailing.com/bugzilla/show_bug.cgi?id=6181">bug 6181</a>.
35 56
</ul>
36 57
<h2 class="articleSubheadline">October 2025</h2>
37 58
<ul class="bulletList">