This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a change to branch
UNOMI-972-credentials-profile-binding-privileged-rest
in repository https://gitbox.apache.org/repos/asf/unomi.git
discard fae021f6d UNOMI-972: close the systemProperties gate on the bare key,
not just the prefix
discard e196fa67e UNOMI-972: cover the context/eventcollector behaviour the
hardening could have broken
discard 2179ed211 UNOMI-972: stop Groovy uploads executing at compile time,
and keep untrusted input out of the logs
discard 8a40ed2b9 UNOMI-972: fix stale public-caller docs and cover the
V2-compat blank-password guard
omit 8e2beeb69 UNOMI-972: make the login sample setup script fail loudly,
not silently
omit cacdaadbc UNOMI-972: fix second-round review findings and simplify the
login sample
omit 08b1fe638 UNOMI-972: address review findings on credentials and
profile binding
omit b01ce305c Potential fix for pull request finding 'CodeQL / Insecure
randomness'
omit a383817bb UNOMI-972: rewrite login sample for trusted server-side merge
omit b8d426958 UNOMI-972: explain why cookie profile binding is safer than
body profileId
omit 2144d3429 UNOMI-972: document client-facing hardening and migration
impact
omit e85fd2976 UNOMI-972: require explicit passwords and tighten public
profile binding
new 899ef37b1 UNOMI-972: require an explicit admin and health-check
password at startup
new 6e9a7d30e UNOMI-972: bind public context callers to the profile cookie
only
new f5b60ab06 UNOMI-972: restrict Groovy action upload to system
administrators
new 04d1c4579 UNOMI-972: restrict router import/export configuration to
system administrators
new 4c970681a UNOMI-972: gate cross-profile merge and systemProperties
writes on a trusted caller
new 3a0bb091a UNOMI-972: rewrite the login sample to demonstrate the
trusted server-side pattern
new cc7728a53 UNOMI-972: prove the hardening end to end, and pin what it
must not break
new 532d855d5 UNOMI-972: document the client-facing changes and the
migration impact
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (fae021f6d)
\
N -- N -- N
refs/heads/UNOMI-972-credentials-profile-binding-privileged-rest (532d855d5)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 8 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../services/impl/GroovyActionsServiceImpl.java | 88 ----------------------
.../impl/GroovyActionsServiceImplTest.java | 38 ----------
.../rest/service/impl/RestServiceUtilsImpl.java | 7 +-
.../RestServiceUtilsImplProfileBindingTest.java | 26 +++++++
4 files changed, 32 insertions(+), 127 deletions(-)
