1. 23 Nov, 2022 1 commit
  2. 18 Nov, 2022 9 commits
  3. 17 Nov, 2022 9 commits
  4. 16 Nov, 2022 2 commits
    • Jérome Perrin's avatar
      *: add some missing security declaration on component code · 8be39d34
      Jérome Perrin authored
      This does not seem to be an actual problem because the object is
      declared protected, but these missing security declarations make
      testSecurity fail.
      8be39d34
    • Jérome Perrin's avatar
      testSecurity: don't skip portal_components in test_method_protection · e300e3f6
      Jérome Perrin authored
      We have been using `filter(lambda x:'/erp5/' in x[0], error_list)` as a
      way to see only missing declarations from ERP5 code, but only ERP5
      filesystem code contains /erp5/ in the filenames, in-ZODB components
      filename is set to something like <portal_components/document.erp5.FTPConnector>
      
      Change to also check methods for which filename contains <portal_components
      and also to print the ignored methods
      e300e3f6
  5. 10 Nov, 2022 4 commits
  6. 08 Nov, 2022 12 commits
  7. 07 Nov, 2022 3 commits
    • Jérome Perrin's avatar
      hal_json_style: adjust transaction interactions in the test · 52b25e02
      Jérome Perrin authored
       - the transaction is aborted in tearDown, no need to abort
        explicitly, for same reason if we want to delete documents, we
        need to explicitly commit (see TestERP5Person_getHateoas_mode_search)
       - simulate decorator should not commit the transaction to keep this
        semantic of abort by default, which keeps test isolated.
      52b25e02
    • Jérome Perrin's avatar
      hal_json_style: fix double translation of worklist message · d7f6bf12
      Jérome Perrin authored
      There was a regression with 45c03413 (hal_json_style: prevent a
      translation of worklist with document count, 2021-05-10), the title
      of the worklist was translated twice. This was supposed to be
      catched by the test, by checking that the mocked gettext had only
      one call for "Draft to Validate", assuming that the translation of
      "Draft to Validate" was "Draft to Validate" and that a double
      translation would cause this to be translated twice, but because of
      a side effect of another test inserting a translation for
      "Draft to Validate", this problem was not noticed.
      
      This fixes the double translation and adjust the test to not depend
      on the actual content of message catalog.
      d7f6bf12
    • Gabriel Monnerat's avatar
      erp5_stripe: introduce new module and features to handle Stripe checkout and payments in ERP5 · d0b448a2
      Gabriel Monnerat authored
      This business template contains a framework to integrate stripe checkout payments in ERP5.
      
      To configure the connector:
      
       - Create an account on stripe.com
       - In stripe.com's dashboard: Developers / API keys use "Create restricted key" to create a key with write access to "All Checkout resources".
       - Create a stripe connector in portal_web_services. Set URL to `https://api.stripe.com/v1/` and the restricted key created in the previous step
       - In stripe.com's dashboard: Developers / Webhooks use "Add endpoint", with "Endpoint URL" set to https://your.erp5.public.hostname/ERP5Site_receiveStripeWebHook and "Events to send" including all events from "checkout.session" category.
      
      To integrate in an ERP5 project:
      
       - Implement a custom script to start a checkout session. The script should call `StripePaymentSessionModule_createStripeSession` to initiate the session and redirect the end user to stripe checkout page.
       - Implement an interaction workfow on `Stripe Payment Session.complete` which inspects the value of `state_change['kwargs']['payment_status']` and implement the logic (such as create a payment transaction) depending on the status `"paid"` or `"unpaid"`.
      
      Example script to create session
      
      ```py
      web_site = context.getWebSiteValue()
      data = {
        # custom web sections for success and cancel URLs
        "success_url": web_site.stripe_payment_session_success.absolute_url(),
        "cancel_url": web_site.stripe_payment_session_cancel.absolute_url(),
        "line_items": {
            "price_data": {
              "currency": "EUR",
              "unit_amount": 2000, # for 20.00 EUR
              "product_data": {
                "name": "Product Name",
              }
            },
            "quantity": 1
          }
      }
      
       # this will redirect the user to stripe checkout page
      return module.StripePaymentSessionModule_createStripeSession(
        connector,
        data,
        context.getRelativeUrl(),
        resource="service_module/...",
      )
      ```
      
      Example interaction workflow script
      
      ```py
      if state_change['kwargs']['payment_status'] == 'paid':
        portal.accounting_module.newContent(
          portal_type='Payment Transaction',
          causality_value=state_change['object'],
          description="Stripe checkout ...",
          ...
        )
      
      ```
      
      Implementation notes:
      
      * Add new stripe connector in ERP5 to access retrieve Stripe session
      * New ERP5 functional module to handle Stripe Payment Sessions
      * Stripe Payment Session reflects a payment transaction/session initiated using the Stripe Checkout solution.
      * Workflow associated with Stripe Payment Sessions provides for the "draft", "open", "completed" and "expired" states in order to reflect the existing states on Stripe.
      * Each Stripe Payment Session offers a history and complete traceability of the HTTP exchanges carried out between ERP5 and Stripe from the start and the end of the payment transaction. All Stripe API calls (createSession, retrieveSession) and Stripe webhook POSTs are logged as system events (HTTP Exchange ERP5) related to a Stripe Payment Session.
      * Add alarm to handle Stripe Payment Sessions open whose date are expired
      * Set web service as source in Stripe Payment Session
      Reviewed-by: Jérome Perrin's avatarJérome Perrin <jerome@nexedi.com>
      Reviewed-on: !1656
      d0b448a2