Skip to content

Conversation

@johanib
Copy link
Contributor

@johanib johanib commented Oct 28, 2025

Continued from #1819

In order to facilitate fine-grained access to SRAM, EB integrates with SRAM through the SBS service.

This process is only enabled if both the feature_enable_sram_interrupt feature flag is enabled and the collabEnabled coin of the SP is true.

If enabled, the SramInterruptFilter will call SBS with the sessionId.
If the sessionId is known in SBS, EB will merge the attributes supplied by SBS into the Auth request.
IF the sessionId is unknown, later in the Consume Assertion process, the browser will be redirected to SBS,
which will redirect back to EB after a successful check. Then the attributes from SBS will be merged after all.

See #1804 for details.

mrvanes and others added 28 commits October 21, 2025 11:01
Add processSRAMInterrupt route

Working SRAM interrupt route

Manipulate attributes in interrupt

Add token parameter

Rename endpoints
Align EB/stub with real SBS authz parameters

Use SBS api namespace
…led-services skip the IdP-SP check. I.e., if coin:collab_enabled is set, skip the check if the correct IdP is connected, and always allow the flow to continue.
Prior to this change, the test still assumed the entitlements call was used.
This change adjusts the test to prime the sbs functional test endpoint for multiple calls on the authz endpoint instead.
@johanib johanib force-pushed the feature/sram-interrupt_rebase_php82 branch from 056d93f to 11ff3d9 Compare October 29, 2025 08:20
@johanib johanib marked this pull request as ready for review October 29, 2025 09:51
Copy link
Member

@MKodde MKodde left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome to see this PR with green builds again 👍

I have some suggestions and questions on the changes of this PR. I know this is the result of a rebase, and most of these points of feedback should be on the 'parent' PR. But still... here you go :)

Prior to this change, stepup would be performed after the SRAM interrupt check.
This change ensures steupup is performed first.
The reason is that the SRAM callout could trigger a 2fa check in SBS. It would be weird to perform a 2fa stepup after that 2fa check.
So doing the stepup first would seem better.
@johanib johanib changed the title SRAM feature rebased Feature: Add SRAM integration through SBS Nov 3, 2025
@baszoetekouw baszoetekouw added this to the 7.1.0 milestone Nov 11, 2025
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.

Connect SBS as external authorization engine to Engineblock

5 participants