Make the servercomponent more public cloud friendly

Answered

Hans Vos

• March 24, 2020 10:47
• Edited

We have two "issues" with the service:

Permissions needed to SBO-COMMON
If we want to set up the service, it requires permissions to the SBO-COMMON database.
In a public cloud setup you don't want to give a partner permissions to the SBO-COMMON. 

Configuration of the service:
The server component now requires a lot of information

• Boyum portal account
• Database user (with permission to the SBO-COMMON database)
• Business One user

If we as a public cloud provider want to set it up we need al that data from our partners.

If after some time the used Business One user changes his password, or the customer migrates to another service unit we as a public cloud provider needs to update the data in the service. 

It would be nice if a partner could set it up from the Boyum portal and that the portal pushes the correct connection details into the service. 
So we install a service that generate some kind of ID and access code, the partner connects to it from the Boyum portal and that way he can manage the service without having access directly to the server.

 

Kind regards,

Hans Vos
Databalance Services B.V.  (Public and Private cloud provider)

Vote

0

• Official comment

  

  Rasmus Jensen

  • March 24, 2020 13:39

  Hi Hans

  The current requirement is not really easy to get rid of as they are the base requirements for the DI-API (except for the notes at the end of this comment).

  Long term when:

  1. Enough people are on an SAP Business One version that can run Service Layer.
  2. The Service Layer can do custom SQL Request

  Then it could be changed, but right now the requirements are SAP's than ours :-/

  Other Notes: 

  1. We have an internal open todo to see if we could get rid of the need for the user to have access to SBO-COMMON. In fact the early CRMFO version did not have the requirements as it got needed databases via DI-API, but due to various SAP bugs that made everything very very slow and crashed a lot... So we chose to take the dependency for the greater good of the product.

  2. The requirement of a portal account will never be removed. It is the only option we have of securing that the person setting up are granted permission to do so.

   

   
• 

  SSP Automation

  • March 24, 2020 10:50

  Thank you for your request. It has been scheduled for review by the development team that will get back to you should there be questions.
  (Please note that as we are user-driven we can't guarantee that your request will be met unless it gets many votes and/or fit the product vision)
  Read more about the Feature Request process here
  [Internal Id: 18068]
  
• 

  Rasmus Jensen

  • April 18, 2020 08:13

  We have now implemented that CRMFO Server Component do not need access to SBOCommon database anymore. This change will be out in the May 11th release (2020.05)

  If this change goes without issues we will do the same for iPayment and B1UP in their June releases

Please sign in to leave a comment.