EmailItem ( email_data ) if inbox_behaviours. unit_of_work () email_item = inbox_behaviours. commit () Example customizations ¶ĭef _handle_email_message ( app : LimeApplication, email_data : dict ): uow = app. ![]() process_email ( app, email_item, uow ) return uow. is_autoreply : # If the incoming e-mail is an auto-reply return inbox_behaviours. have_email_been_processed ( app, email_item ): # If the incoming e-mail is being processed or has been processed return False elif email_item. add_resource ( Recovery, "/inbox/recover/" ) def _handle_email_message ( app : LimeApplication, email_data : dict ): uow = app. ![]() add_resource ( Notification, "/inbox/" ) class Recovery ( RecoveryResource ): def post ( self, app, email_data ): return _handle_email_message ( app, email_data ) api. import api from limepkg_ms_inbox.ms.api.resource import ( NotificationResource, RecoveryResource, with_notification, with_recovery, ) import limepkg_ms_inbox.behaviours as inbox_behaviours class Notification ( NotificationResource ): def post ( self, app, email_data ): return _handle_email_message ( app, email_data ) api. If you don't you will get a error like this:įrom lime_application.application import LimeApplication from. Make sure that the Service user running the Lime services have read access to the file you specify. When specifiyng the path, make sure to escape the backslashes ( \) by using two backslashes for each. How many "sync & save" logs to store for each client.Ī list of additional $select properties to send to Ms Graph api, read more about it here. Read more details here be able to support self-signed certificatesĬonfig.limepkg_ms_inbox.sync_history_length NameĬonfig.limepkg_ms_to_verify_certĪ full path to a cert file that will be used to verify the SSL cert when using the recovery functionality. Usually you don't have to set any of these, but can sometimes be needed. To fix this we need correct values for client_id, tenant_id and client_secret. If something is wrong you should recieve an error message in the bottom of this page. You can click Validate it checks that you have provided valid ids and secret. If you go to Lime Admin after this your should see something similar to this: Of your client and can be set to whatever you want) Replace with your solution name, and put whatever you wantįor client_id, tenant_id and client_secret. If you add the config above in the application_config.yaml file. However, you should be able to verify that a client shows up in Lime Admin These values are created and given to the consultant by the customer ( See azure enterprise application setup on how to set this up) Where client-id, tenant-id and client-secret are used to authenticate to a specific Enterprise Application in Azure. Configuring clients ¶Ī client in this context is a connection to the Microsoft Graph API which is needed to connect and authenticate. This is done by adding several with corrensponding configurations and secrets in your application_config. Lime Inbox support the use of several Azure Applications in one Lime Application. Go your application config and replace the following: ![]() Update Lime CRM's application config with the credentials and secret from the customer. The URL patterns that must be exposed can be found here. Commonly, our customers use a combination of proxies, reverse-proxies, DMZ, and of course, firewalls. Public access (on-premise only) ¶įor Lime Inbox to work, some parts of the Lime CRM server must be exposed to the internet to allow Microsoft's services to communicate with Lime.Įither full public access to the server can be given, or access can be restricted to the specific endpoints that Lime Inbox use.Įxactly how to minimize the exposure is up to the customer's IT department to solve. If the customer wants to limit the access of the application to a specific mailbox, see Limiting application permissions to specific Exchange Online mailboxes (Microsoft Docs). Per default Microsoft grants access to all Inboxes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |