(Supporting Network Advisor 12.3.0)
Table Of Contents
- Contents
- About This Document
- Overview of the Network Advisor REST API
- Getting Started
- Using the Brocade Network Advisor REST API
- Introduction
- Logging in and out
- Specifying content type
- Versioning (backward compatibility)
- Using the Topology API
- Using the SAN Fabric Discovery API
- Using the Traffic Flow API
- Using the Summary Data API
- Using the Events API
- Using the Zoning API
- Using the Historical Performance Data API
- Fibre Channel Routing
- Handling errors
- Use Cases
- API Reference
- Request and Response Schemas
- Topology
- SAN fabric discovery
- Summary data
- SummaryResponse
- StatusSummary
- AssetClassificationSummary
- NetworkObjectCountSummary
- EventsSummary
- BottleneckViolationsSummary
- OutOfRangeViolationsSummary
- PortHealthViolationsSummary
- VmViolationsSummary
- SummariesResponse
- PortsMonitorSummaryData
- MonitorDistributionData
- ProductsMonitorSummaryData
- FlowMonitorSummaryData
- Events
- Zoning
- Historical performance data
- Authentication and session management
24 Brocade Network Advisor REST API Guide
53-1003160-01
Logging in and out
3
org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatch
er.java:264)
org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousD
ispatcher.java:209)
org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.j
ava:557)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:5
24)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:1
26)
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(Serv
letContainerDispatcher.java:208)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServl
etDispatcher.java:55)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServl
etDispatcher.java:50)
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)</pre></p><p><b>JBWEB
000071: root cause</b> <pre>RSException [errorCode=4005, errorMsg=Invalid
username or password]
com.brocade.dcm.webservices.server.util.WebServiceCommonUtil.throwException(WebSe
rviceCommonUtil.java:98)
com.brocade.dcm.webservices.server.sessionmgmt.WebSessionManager.validateUsername
Password(WebSessionManager.java:485)
com.brocade.dcm.webservices.server.sessionmgmt.WebSessionManager.createSession(We
bSessionManager.java:169)
com.brocade.dcm.webservices.server.security.LoginRequestInterceptor.preProcess(Lo
ginRequestInterceptor.java:105)
com.brocade.dcm.webservices.server.security.LoginRequestInterceptor$Proxy$_$$_Wel
dClientProxy.preProcess(LoginRequestInterceptor$Proxy$_$$_WeldClientProxy.java)
org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:247)
org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:222)
org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:211)
org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.j
ava:542)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:5
24)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:1
26)
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(Serv
letContainerDispatcher.java:208)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServl
etDispatcher.java:55)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServl
etDispatcher.java:50)
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)</pre></p><p><b>JBWEB
000072: note</b> <u>JBWEB000073: The full stack trace of the root cause is
available in the JBoss Web/7.2.0.Final logs.</u></p><HR size="1"
noshade="noshade"><h3>JBoss Web/7.2.0.Final</h3></body></html>
Logging out
Use the /logout POST URI to log out. Successful completion of the request results in the deletion of
the client session. The logout request does not require any request payload except for the session
token, which must be passed in an HTTP header parameter. Because there is no return value to
this request, an HTTP status code of 204 (No Content) is returned upon success.
<BASE_URI>/logout