# Web Service Attributes Editor: Quality of Service: Security

In the Security section of the WSIT configuration editor, you may configure a user name and password for some of the security mechanisms.

Element | Description
--- | ---
Use development defaults | Fast Infoset is a more efficient alternative to XML. If the service is configured to allow Fast Infoset, select this option to use Fast Infoset for faster parsing, faster serializing, and smaller document sizes when compared with equivalent XML documents.
Authentication Credentials | If selected, the client runtime checks to see if the service supports TCP, and, if so, the client uses TCP transport automatically for service-client communication. TCP provides better performance when sending smaller messages. The performance enhancement is visible mostly in smaller messages because the overhead of sending messages over the HTTP protocol is eliminated. If the service does not support TCP, or if this option is not selected for the client, HTTP is used for transport.
Static |
Default Username |
Default Password | Enter the name of an authorized user and the password for this user. This option is best used only in the development environment. When the Default Username and Default Password are specified, the username and password are stored in the wsit-client.xml file in clear text, which presents a security risk. Do not use this option for production.
Dynamic |
Username Callback Handler |
Password Callback Handler | If you create JSR-109-compliant web services and web service clients that run under an Application Server container (JSR-109 deployment), the container handles the callbacks and you do not need to configure Callback Handlers of your own. If you are using another container, select the Browse button to select the class implementing the `javax.security.auth.callback.CallbackHandler` interface.
SAML Callback Handler | To use a SAML Callback Handler, you need to create one, as there is no default.

Related Topics

Developing Applications with NetBeans IDE,

Copyright © 2016, Oracle and/or its affiliates. All rights reserved.