blob: 8ef70eced2e0ce996fd067064b01b56431f7de60 [file] [log] [blame]
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Custom-Authentication</title>
</head>
<body>
<p>The ChannnelSet.login() and ChannelSet.logout() methods are the preferred methods for setting and removing credentials. In the previous release of LiveCycle Data Services, you sent credentials to a destination by calling the setCredentials() method of a component such as RemoteObject, Producer, Consumer, WebService, or HTTPService. The setCredentials() method did not actually pass the credentials to the server until the first attempt by the component to connect to the server. Therefore, if the component issued a fault event, you could not be certain whether the fault happened because of an authentication error, or for another reason. </p>
<p>In the Basic Authentication sample, the code did not use the login() and logout() methods before subscribing to the destination, and as a result, the web browser prompts you to log in before you can access data. </p>
<p>&nbsp;</p>
</body>
</html>