Skip to content

Conversation

@fmoessbauer
Copy link
Member

@fmoessbauer fmoessbauer commented Jan 7, 2026

This PR makes the acquisition of PRT SSO cookies compatible with broker versions > 2.0.1. If fetching the device state information and profile picture works depends on more factors, as discussed in #114 .

With the limited support for 2.0.2+, we still keep the banner in the readme regarding compatible broker versions. Once the remaining issues on the newer broker versions are sorted out, we can remove the note.

Note, that the dbus interface changes are based on our experiments in siemens/sso-mib#26.
The webextension part is still fully compatible with older native (python script) versions, however to get support for new brokers both components need to be updated.

If we have a sso_url (which is only used for the PrtSsoCookie), we need
to use type 8. Otherwise the type is 1 (as observed via DBus).
This change is needed for brokers > 2.0.1.

Xref: #108
Signed-off-by: Felix Moessbauer <[email protected]>
The account is only needed as part of the authorization params, hence we
do not need to add it to the higher-level params.

Xref: #108
Signed-off-by: Felix Moessbauer <[email protected]>
In case the broker is newer than v2.0.1, the cookie data is further down
in the json response data. Account for that.

Xref: #108
Signed-off-by: Felix Moessbauer <[email protected]>
Brokers > 2.0.1 do not implement the introspection interface. To
mitigate this, we create the dbus proxy object directly from a local
copy of the dbus broker interface spec.

Xref: #108
Signed-off-by: Felix Moessbauer <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants