You can use only the security token types that are supported by ACS, namely, SAML 1.1, SAML 2.0.
#LOGITRACE V14 SETUP PASSWORD FOR INSTALETION WINDOWS#
If you use the AccessControlService credential type, then authentication is handled by Windows Azure AccessControlService (ACS) or Microsoft Azure Active Directory (Microsoft Azure AD) for user authentication services. This mode is intended for hosted environments, for example, where Business Central is implemented in Windows Azure and the list of allowed users is maintained by Business Central and not based on Windows users. Security certificates are required to protect the passing of credentials. The credentials are then validated by an external mechanism. The user is prompted for username/password credentials when they start the client.
If you use the NavUserPassword credential type, then authentication is managed by Business Central Server but is not based on Windows users or Active Directory. This setting should typically be used when the computer on which Business Central Server is installed is part of an authenticating Active Directory domain but the computer where the client is installed is not part of the domain. Security certificates are required to protect the passing of credentials across a wide-area network. There must already be a corresponding user in Windows. These credentials are then validated against Windows authentication by Business Central Server. If you use the UserName credential type, then the user must specify username/password credentials on the client. With the Windows credential type, X.509 certificates are not used. Typically, it is used on a LAN with Active Directory. This user must be known to both the server and the client. If you use the Windows credential type, then the client connects with current user. Possible values are: Windows, Username, NavUserPassword and AccessControlService. The type of client credential used for client authentication. This example prompts for ServiceAccount credentials and then creates a new Business Central Server instance. VERBOSE: Setting service parameter: 'ODataServicesPort' to value: '8102' VERBOSE: Setting service parameter: 'SOAPServicesPort' to value: '8101' VERBOSE: Setting service parameter: 'ClientServicesPort' to value: '8100' VERBOSE: Setting service parameter: 'ManagementServicesPort' to value: '8099' VERBOSE: Installing Server Instance MicrosoftDynamicsNavServer$NewInstance VERBOSE: Creating Instance directory C:\Program Files\Microsoft BC\130\Service\Instances\NewInstance VERBOSE: Performing operation "New-NAVServerInstance" on Target "ServerInstance = MicrosoftDynamicsNavServer$NewInstance, DatabaseInstance = ". EXAMPLE 2 Get-Credential | New-NAVServerInstance NewInstance -ServiceAccount User -ManagementServicesPort 8099 -ClientServicesPort 8100 -SOAPServicesPort 8101 -ODataServicesPort 8102 -verbose It configures the necessary firewall exceptions and performs the necessary Access Control List registrations. This example creates a new Business Central Server instance. VERBOSE: Adding Windows Firewall (and UrlAcl) rules for Server Instance MicrosoftDynamicsNavServer$NewNAVServer VERBOSE: Creating Instance directory C:\Program Files\Business Central\130\Service\Instances\NewNAVServer Examples EXAMPLE 1 New-NAVServerInstance NewInstance -ManagementServicesPort 8099 -ClientServicesPort 8100 -SOAPServicesPort 8101 -ODataServicesPort 8102 -verbose All permissions that are required for the instance to start are configured automatically. Make sure that you verify the DatabaseServer and DatabaseName values after the instance is created, to ensure that the instance can accept client requests. You must specify a name for the instance, in addition to values for the four port parameters.Īll other configuration values for the new instance are based on default values.
Use the New-NAVServerInstance cmdlet to create a new Business Central Server instance. In this article Syntax New-NAVServer Instance Creates a new Business Central Server instance.
0 kommentar(er)
