History | Log In     View a printable version of the current page.  
Issue Details (XML)

Key: SDK-13646
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Assignee: Dave Stanten
Reporter: Ed Solovey
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Flex SDK

RemoteObject.setCredentials does not callback a Fault Event if it is called after some initial communication with endpoint

Created: 11/19/07 06:16 PM   Updated: 12/01/07 10:28 PM
Component/s: RPC: RemoteObject
Security Level: Public (All JIRA Users )

Severity: Incorrectly Functioning
Reproducibility: Every Time
Discoverability: Low
Found in Version: None
Milestone:
Affected OS(s): All OS Platforms
Steps to Reproduce:
Steps to reproduce:
1. Invoke a RemoteObject operation on a destination that does not have a security constraint
2. Call RemoteObject.setCredentials() such that the call fails - with invalid credentials for example
 
 Actual Results:
Attempt to login fails on server but no callback is invoked on client
 

 Expected Results:
A callback on the client should be invoked. It could potentially be the same mx.messaging.events.ChannelFaultEvent.FAULT that gets called back when the initial ping for the Channel fails.
 
 
 
 
Language Found: English
Bugbase Id: none
Triaged: Yes
Regression: No
QA Owner: Trevor Baker
Resolved by: Ed Solovey
Participants: Dave Stanten, Ed Solovey, Lauren Park and Trevor Baker
Browser: Firefox 2.x
JDK: Sun 1.5.x


 All   Comments      Sort Order:
Ed Solovey - [11/27/07 09:41 AM ]
This should be resolved via change 188966:

MessageAgent.as and AsyncRequest.as
* Introduced new hasPendingRequestForMessage method that allows Channel.as to determine in its statusHandler whether a channel fault needs
to be raised for a failed authentication attempt.

Channel.as
* Use the hasPendingRequestForMessage method introduced in AsyncRequest to raise a channel fault when setCredentials() fails
after the initial client-server connection has been established.

Trevor Baker - [12/01/07 02:26 PM ]
To Dave for verification

Dave Stanten - [12/01/07 10:26 PM ]
Confirmed fix:
server side shows:
[Flex] 23:09:29.062 [ERROR] [Message.General] Error handling message: flex.messaging.security.SecurityException: Invalid login.

fault returned to client:
(mx.rpc::Fault)#0
  errorID = 0
  faultCode = "Channel.Authentication.Error"
  faultDetail = "Invalid login."
  faultString = "warn"
  message = "faultCode:Channel.Authentication.Error faultString:'warn' faultDetail:'Invalid login.'"