Skip to content

(fix): internal access#782

Merged
ehayes2000 merged 5 commits intomainfrom
fix-internal-access
Jan 6, 2026
Merged

(fix): internal access#782
ehayes2000 merged 5 commits intomainfrom
fix-internal-access

Conversation

@ehayes2000
Copy link
Copy Markdown
Contributor

  • fix internal access
  • error code

Internal access was broken with e2b8be8 which updated user id parsing. This
updates the internal user id to be compatible with new parsing.

Internal access is a blight on the codebase, but is still a dependency of DCS.

Copy link
Copy Markdown
Contributor

@seanaye seanaye left a comment

Choose a reason for hiding this comment

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

aids

request: MarkdownRewrite,
scribe: &ToolScribe,
_user_id: &str,
jwt: &str,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nit: ask for what you need, we need an owned String so this should take a String

let user_id = user_context.user_id.clone();

if matches!(user_id.as_str(), "" | "INTERNAL") {
if matches!(user_id.as_str(), "" | MACRO_INTERNAL_USER_ID) {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'm curious whats going on here? What is the motivation for this change? This suggests that something was being allowed in that shouldn't have access

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Yea you've pretty much got it. The internal access endpoints use a custom user id and grant owner permissions to stuff. Its aids. It's an old system that should be replaced by sending a jwt (which is why I changed endpoints where it was easy).

@ehayes2000 ehayes2000 merged commit 234fa7b into main Jan 6, 2026
37 checks passed
@ehayes2000 ehayes2000 deleted the fix-internal-access branch January 6, 2026 15:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants