SafeNet Sentinel, Руководство разработчика

Страница: 72 / 282

Chapter 3 – Planning Application Protection and Licensing Strategy
54 Sentinel Hardware Keys Developer’s Guide
Enabling License Sharing
The decision to share licenses depends on your licensing policy. To enable
license sharing:
■
For Shell-protected applications, you can specify ON in the License
sharing option (under the
Networking tab).
■
For API-protected applications, you need to call the SFNTGetLicense
function with the SP_SHARE_ON flag.
Are you protecting applications for a stand-alone or
network environment?
This decision will help you in choosing the type of Sentinel Key you want to
ship with your protected application. Please note that a stand-alone key
cannot provide licenses to network users; while, a network key can provide
licenses to users across LAN/WAN.
In addition, you will also need to decide the access mode you want to set in
your application. For extensive and busy networks, you can ship a client-
side configuration file with your protected application.
About Access Modes
An access mode determines the route a protected application follows to
obtain a license. Sentinel Keys Toolkit allows you to use one of the following
access modes:
■ Stand-alone mode (SP_STANDALONE_MODE)
The application looks for a license on the same system without
requiring the Sentinel Keys Server (it directly accesses the Sentinel
System Driver). If the required Sentinel Key is not attached to the
system, an error is returned.
■
Server mode (SP_SERVER_MODE)
The application obtains a license from a network key. It does not look
for a stand-alone key. A specific host can be set using the
SFNTSetContactServer API function or the client-side configuration
file. Else, the license request will be broadcasted within the subnet.