Skip to content
Permalink
Browse files
Merge branch 'release/1.8' into develop
  • Loading branch information
pivotal-amurmann committed Dec 12, 2018
2 parents c91ab3d + ae8c6b2 commit 3cea07343a3dc6ba2cc739bcdbf370ff212ad089
Show file tree
Hide file tree
Showing 4 changed files with 14 additions and 39 deletions.
@@ -1,17 +1,16 @@
/\\.git/
/\\.DS_Store
/\.git/
/\.DS_Store

/build-.*/

/build/
/\\.settings/
/\\.cproject
/\\.project
/\\.idea/
\\.vs/
\\.vscode/
/\.settings/
/\.cproject
/\.project
/\.idea/
\.vs/
\.vscode/

/examples/dotnet/.*/bin/
/examples/dotnet/.*/obj/
\\.ruby-version

\.ruby-version
@@ -23,11 +23,6 @@ if (MSVC)
#define APACHE_GEODE_EXTERN_TEMPLATE_EXPORT
")

target_compile_options(apache-geode
PRIVATE
/bigobj # C1128 - large number of templates causes too many section.
)
else()
set(EXPORT_HEADER_CUSTOM_CONTENT "
#define APACHE_GEODE_EXPLICIT_TEMPLATE_EXPORT
@@ -85,10 +85,6 @@ limitations under the License.
</ul>
</li>
<li>
<a href="/docs/geode-native/<%=vars.product_version_nodot%>/function-execution/function-execution.html">Function Execution</a>
</li>
<li>
<a href="/docs/geode-native/<%=vars.product_version_nodot%>/transactions/transactions.html">Transactions</a>
</li>
@@ -19,25 +19,19 @@ See the License for the specific language governing permissions and
limitations under the License.
-->

A client is authenticated when it connects with valid credentials to a <%=vars.product_name%> cache server that is configured with the client authentication callback.
A client is authenticated when it connects with valid credentials to a <%=vars.product_name%> cache server that is configured with the client `Authenticator` callback.
For details on the server's role in authentication and what it expects from the client, see [Implementing Authentication](geodeman/managing/security/implementing_authentication.html) in the *<%=vars.product_name%> User Guide*.

Examples of various implementations can be found in the Native Client source distribution's `../templates/security` directory.

In your application, authentication credentials must be set when creating the cache. In practice,
this means setting the authentication credentials when you create the CacheFactory.

### .NET Authentication Example

The following excerpt is taken from the .NET example provided with your Native Client distribution in the `../examples/dotnet/AuthInitialize` directory.
In this C# authentication example, credentials are implemented in the GetCredentials member function of the ExampleAuthInitialize class, which implements the IAuthInitialize interface.

In this C# authentication example, the `CacheFactory` creation process sets the authentication callback:

```cs
var cacheFactory = new CacheFactory()
.Set("log-level", "none")
.SetAuthInitialize(new ExampleAuthInitialize());
```

Credentials are implemented in the `GetCredentials` member function of the `ExampleAuthInitialize` class, which implements the `IAuthInitialize` interface:

```cs
class ExampleAuthInitialize : IAuthInitialize
@@ -70,16 +64,7 @@ Credentials are implemented in the `GetCredentials` member function of the `Exam

### C++ Authentication Example

In this C++ authentication example, the `CacheFactory` creation process sets the authentication callback:

```cpp
auto cacheFactory = CacheFactory(config);
auto authInitialize = std::make_shared<UserPasswordAuthInit>();
cacheFactory.set("log-level", "none");
cacheFactory.setAuthInitialize(authInitialize);
```

Credentials are implemented in the `getCredentials` member function of the `AuthInitialize` abstract class.
In this C++ authentication example, credentials are implemented in the getCredentials member function of the AuthInitialize abstract class.

```cpp
class UserPasswordAuthInit : public AuthInitialize {

0 comments on commit 3cea073

Please sign in to comment.