Conversation
- Updated .env.example and .env.local_dev to include new SMTP configuration options. - Refactored email sending logic in OpenSignServer to utilize new utility functions for resolving sender email and formatting headers. - Improved error handling for invalid email configurations. - Ensured compatibility with both SMTP and Mailgun email sending methods.
- Added a new mailcatcher service to docker-compose for testing email delivery. - Introduced global email branding configuration, allowing customization of email logos, colors, footers, and wrappers. - Updated email sending functions to apply branding settings dynamically. - Created utility functions for fetching and updating email branding configurations. - Enhanced email templates to support branding tokens for consistent styling across all email communications. - Documented the new email branding feature in EMAIL_BRANDING_EXTENSION.md.
* feat: Implement SSO login and configuration support - Added OAuth2/OIDC SSO configuration options to .env.example for issuer and client ID. - Updated entrypoint script to include new environment variables for SSO. - Introduced AuthCallback component to handle SSO authentication flow. - Enhanced Login component with SSO login functionality and PKCE support. - Implemented user profile updates to reflect SSO user information. - Added server-side SSO login handling and user validation in OpenSignServer. - Updated user signup process to accommodate SSO users and role mapping. - Documented SSO integration in the application. * feat: Enhance SSO functionality and user state management - Updated .env.example to clarify SSO configuration options. - Introduced state nonce management in AuthCallback and Login components for improved OAuth flow. - Enhanced error handling for invalid OAuth states during authentication. - Added utility function for safe JSON retrieval from local storage in UserProfile component. - Improved user profile handling by ensuring consistent state management and display of user information.
* feat: Add SDK Sign Requests API implementation - Introduced a new Parse Cloud Function for creating signing requests via the SDK. - Implemented authentication using Bearer tokens validated through Authentik introspection. - Added detailed API documentation for the new endpoint, including usage examples and limits. - Established constraints for signers, positions, and PDF size to ensure proper request handling. * refactor: Update environment variables and SDK authentication for OAuth2 integration
- Modified Caddyfile to include a new handle for reverse proxying client requests. - Implemented createBatchDocs function in OpenSignServer to handle batch document creation with validation for user authentication and document format.
* confidential-sso * gitignore
…gh (#14) * docs: fix stale 'both' reference in metadata spec architecture diagram Made-with: Cursor * docs: add sign request metadata implementation plan Made-with: Cursor * feat(metadata): accept and validate metadata in sdkSignRequests Extracts a pure validateMetadata helper (exported for testing), reads the optional metadata param from the request, and spreads it as Metadata into the doc object passed to batchdocuments. Made-with: Cursor * test(metadata): assert Parse.Error type and code 400 in validateMetadata tests Replace bare toThrowError() with toThrowMatching(err => err instanceof Parse.Error && err.code === 400) in all 5 throw cases so that wrong error types or codes would cause failures. Also add spec/helpers/parseInit.js (lightweight Parse global init without a server) and spec/support/jasmine.metadata.json so the metadata spec can run in isolation without the full Parse Server / MongoDB infrastructure. Update spec/utils/test-runner.js to read MONGODB_URI from the environment so the test database URI is configurable. Made-with: Cursor * fix: correct parseInit path in metadata spec comment Made-with: Cursor * feat(metadata): pass Metadata through createBatchDocs to contracts_Document Made-with: Cursor * feat(metadata): include metadata in all three dispatchWebhook payloads Made-with: Cursor * docs: document metadata field in SDK_SIGN_REQUESTS_API.md Made-with: Cursor * docs: update webhook URL description and clarify service role in metadata handling * refactor(metadata): update metadata field keys in SDK sign requests and documentation
* feat: enhance email sender configuration for SDK sign requests - Added new environment variables for SDK sign request email display name and Reply-To address in .env.example. - Introduced a utility function to resolve email sender details in createBatchDocs and sdkSignRequests. - Updated email sending logic to utilize the new sender configuration, ensuring defaults are applied when environment variables are not set. - Added unit tests for the new email sender resolution functionality. * refactor: update email sender configuration and enhance documentation - Changed default email sender address in SDK sign requests and related functions to a more generic no-reply address. - Updated .env.example to reflect the new default sender email and name. - Enhanced development documentation to emphasize the use of Docker for running project commands. - Added unit tests to verify the new email sender logic and fallback mechanisms. * docs: clarify Docker usage and enhance SDK email sender tests - Updated documentation to specify Docker command usage for container execution and one-off runs. - Added a new unit test to verify default email sender behavior when environment variables are blank in SDK sign requests.
Syncs with OpenSignLabs/OpenSign upstream at b417754 (v2.39.0 + server.cjs fix). Custom features preserved: - SSO/OAuth2 login (ssoLogin, usersignup SSO flow, getExistingOrgAndTeam) - Global email branding (getGlobalEmailBranding, updateGlobalEmailBranding) - SDK sign requests API (sdkSignRequests cloud function) - Webhooks: document.signed / document.completed (dispatchWebhook in PDF.js) - Per-document callback_url and metadata passthrough - Enhanced email sender config (getResolvedMailSender, formatFromHeader, getSmtpEnvelopeFrom) - Branded email rendering (renderBrandedEmailHtml in sendMailv3/Utils) - createBatchDocs custom fields (CallbackUrl, Metadata, normalizedSendInOrder) Upstream additions integrated: - createDocumentFromApp cloud function - SendInOrderStrict strict signing order enforcement - Cc field in batch documents and sendMailv3 - workflowUtils (COMPLETION_ACTIVITIES, findPlaceholderIndex, etc.) - sendSystemMail utility - 4 new DB migrations (cc field, templatelinks, normalizedEmail, sendInOrderStrict) - server.cjs static server fix - pdf-lib expanded imports (PDFName, degrees, PDFArray, PDFDict) Co-authored-by: Cursor <cursoragent@cursor.com>
…omponents - Store SSO access token in sessionStorage upon successful authentication in AuthCallback. - Retrieve and utilize the SSO access token in the Login component for user signup. - Clean up sessionStorage by removing the access token after user login process.
Docs: update readme
…n-be feat: implement SSO access token handling
* feat: implement org-scoped access control for OrgAdmins - Added functions to manage organization-specific user access, including `listUserIdsInOrg` and `listOrgAdminUserIdsForOrg`. - Enhanced document ACL management for OrgAdmins in `addUser`, `DocumentAftersave`, `getDrive`, and `getReport` functions. - Implemented backfill logic for existing documents when a new OrgAdmin is added. - Updated document filtering to allow OrgAdmins to access documents created by any member of their organization. - Introduced a migration script to backfill ACLs for existing documents based on OrgAdmin roles. * feat: add report fetching logic for OrgAdmins in DashboardCard component * refactor: streamline user and OrgAdmin management functions - Moved the `backfillOrgAdminAcl` function from `addUser.js` and `usersignup.js` to `orgScope.js` for better organization and reusability. - Updated `listUserIdsInOrg` and `listOrgAdminUserIdsForOrg` to use `query.each()` for efficient pagination, accommodating larger organizations. - Enhanced the migration script to ensure robust handling of ACL updates for OrgAdmins, including error logging and resilience against failures.
Avoid unexpected upgrades from mongo:latest in local Docker Compose. Co-authored-by: Cursor <cursoragent@cursor.com>
|
@damarinov is attempting to deploy a commit to the prafull 's projects Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
mongo:latesttomongo:7.0.43so local stacks do not pick up unexpected major upgrades.Test plan
docker compose pull mongoand confirm the image ismongo:7.0.43Made with Cursor