inPoint.Server
Web.Config
This chapter describes the important settings of the web.config.
Location: "..\H&S Heilig und Schubert Software AG\Pam.Storage\Web\web.config"
Archive configuration
<PamArchiveConfig ExternalFile="" />
- Path to Pam.Archive.config
- This config contains also the database connection string
- Example:
../../Pam.Archive/Pam.Archive.config
LDAP & authentication settings
<add key="LDAPAuthenticationDomain" value=""/>
- The users will be authenticated within this domain(s).
- Multiple domains can be added with a "," seperator.
- Must be full-qualified
- Example:
domain.local, domain2.local
<add key="LDAPAuthenticationUser" value=""/>
<add key="LDAPAuthenticationPassword" value=""/>
- Contains the user account & password to use for connection to active directory.
- Must be full-qualified
- Password must be encrypted.
- Example:
testUser@domain.local
<add key="FallbackNTDomain" value=""/>
- When the inPoint server receives a "weak" user name without a domain = SamAccountName (not FQDN and not DOWNLEVEL_LOGON_NAME), this domain will be used for getting the DOWNLEVEL_LOGON_NAME to find the user in the PAM_USERREFERENCE table.
- Examples:
- User=TestUser, FallbackNTDomain=empty => Error
- User=TestUser, FallbackNTDomain=
domain.local
=> User will be fully qualified and authenticated asTestUser@domain.local
- User=
TestUser@domain.local
=> FallbackNTDomain will be not used.
<add key="identityAuthority" value=""/>
- URL to the identity Server.
- Will be used for authentication.
- Example:
https://testServer.domain.local:5443
<add key="impersonationusers" value=""/>
- Users allowed to impersonate as any other user without the password.
- Multiple usernames are allowed and sparated with ';'
- Example:
Domain\testUser
Server connection URL
<add key="pam4url" value=""/>
- This value will be used by the server. (As example for the loader or WebDav)
- Example:
http://testMachine:80/Pam.Web/
WebDav support
<add key="pamWebDavUrl" value="" />
- This will be used for the WebDav communication.
- If this value is empty => the pam4url + "/webdav" will be used.
- Example:
http://testMachine:80/Pam.Web/webdav
HTTPS support
The following binding must be added to the Unify.WCF & Pam.WCF service endpoints if the server connection should run with HTTPS:
"wsHttpBinding_PamWCF_wia_ssl"
Example:
<service behaviorConfiguration="PamWCFBehavior_wia" name="Pam.WCF.PamWCF">
<endpoint address="/wia" binding="wsHttpBinding" bindingConfiguration="wsHttpBinding_PamWCF_wia_ssl" contract="Pam.WCF.IPamWcf"/>
</service>
<service behaviorConfiguration="UnifyWCFBehavior_wia" name="Pam.Unify.WCF.UnifyWcf">
<endpoint address="/wia" binding="wsHttpBinding" bindingConfiguration="wsHttpBinding_PamWCF_wia_ssl" contract="Pam.Unify.WCF.IUnifyWcf"/>
</service>
Feeds (HTTPS connection): Add the following binding and service endpoint if the Feed connection should run with HTTPS.
Binding:
<webHttpBinding>
<binding name="wbBind_ssl">
<security mode="Transport">
<transport clientCredentialType="Windows" proxyCredentialType="Windows" />
</security>
</binding>
</webHttpBinding>
Service endpoint:
<service behaviorConfiguration="UnifyWCFBehavior_wia" name="Pam.Unify.WCF.UnifyWcf">
<endpoint address="/feed" binding="webHttpBinding" bindingConfiguration="wbBind_ssl" behaviorConfiguration="RESTFeed" contract="Pam.Unify.WCF.IUnifyFeed" />
</service>
Notification service
<PamNotification Retries="5" TestRecipient="">
<SMTPSettings Server="" Port="25" EnableSsl="false" Sender="" SenderName="" User="" Password="" BulkMerge="" />
</PamNotification>
- Configuration section for sending emails.
Log4Net reference
<appSettings>
<add key="log4net.Config" value="..\log4net.config"/>
<add key="log4net.Config.Watch" value="True" />
</appSettings>
- Path to the log4net.config
- Must be not the same directory like "..\Pam.Storage\web\bin" otherwise the IIS will be reset after every change in the file.
Conversion service
<add key="PamConversionServiceWS" value="" />
- URL for the conversion service.
- Example:
net.tcp://TestServer:5100/Pam.Conversion.Service