Skip to content

Conversation

@NL66278
Copy link

@NL66278 NL66278 commented May 14, 2024

No description provided.

@NL66278 NL66278 force-pushed the 16.0-add-base_external_system_ms_client_assertion branch from e22688b to c458b29 Compare May 15, 2024 14:36
@NL66278 NL66278 force-pushed the 16.0-add-base_external_system_ms_client_assertion branch from c9145b2 to ea7dd5f Compare May 22, 2024 08:06
@NL66278 NL66278 force-pushed the 16.0-add-base_external_system_ms_client_assertion branch 2 times, most recently from 1155011 to 990b53f Compare May 29, 2024 12:12
@NL66278 NL66278 changed the title [WIP][16.0] add base_external_system_ms_client_assertion [16.0] add base_external_system_ms_client_assertion Oct 7, 2024
@NL66278
Copy link
Author

NL66278 commented Oct 7, 2024

For some time now successfully running in production at large customer.

SiesslPhillip pushed a commit to grueneerde/OCA-server-backend that referenced this pull request Nov 20, 2024
Syncing from upstream OCA/server-backend (16.0)
@github-actions
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Mar 23, 2025
@NL66278
Copy link
Author

NL66278 commented Mar 24, 2025

@thomaspaulb Could you add a no stale label here?

@github-actions github-actions bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Mar 30, 2025
Copy link

@lfreeke lfreeke left a comment

Choose a reason for hiding this comment

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

👍

This have been working without issues for our customer

@NL66278 NL66278 force-pushed the 16.0-add-base_external_system_ms_client_assertion branch from 584630c to cbe2e26 Compare September 3, 2025 11:02
@github-actions
Copy link

github-actions bot commented Jan 4, 2026

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jan 4, 2026
@thomaspaulb thomaspaulb added no stale Use this label to prevent the automated stale action from closing this PR/Issue. and removed stale PR/Issue without recent activity, it'll be soon closed automatically. labels Jan 5, 2026
@thomaspaulb
Copy link

@NL66278 Sorry, this can't be merged in its current form. It's too many things at once, and covers 4 different modules.

Can we start by opening up a PR to base_external_system, with the refactors that are being done there? Add a description to the PR with checkboxes for each of the things that are added, and the source PR where it comes from (I can't find it, at least it was never merged)

@NL66278
Copy link
Author

NL66278 commented Jan 5, 2026

@thomaspaulb There was this one #281 that was also never merged. All of this is running in production, alt multiple clients, without any problems.

@NL66278
Copy link
Author

NL66278 commented Jan 27, 2026

@thomaspaulb OK, so here is the first PR for the base module. When that is merged, I will provide, one by one, PR's for the additional modules.

@NL66278
Copy link
Author

NL66278 commented Feb 9, 2026

@thomaspaulb Here is the actual link to the first PR, the one to make the base module extendable, #414

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved no stale Use this label to prevent the automated stale action from closing this PR/Issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants