Authentication types and roaming

What is the appropriate authentication type for continuously connected apps?
I recently implemented a wireless solution using 1240AGs, 4425 controllers and WLC.
I?m testing intermec CK31 handhelds connected to an oracle telnet based WMS.
I have WPA2+AES and PEAP authentication enabled.
When the handhelds roam from one AP to the next, it appears to be re-authenticating. This causes the connection and IP to drop and re-establish just slow enough to cause problems with maintaining a session the oracle WMS.
I can see the units re-authenticating in the ACS logs.
Any help or discussion would be appreciated.

EAP-Fast or LEAP are probably your best shot.
Good Luck
Scott

Similar Messages

Using OLAP Connection for SAP BW based on authentication type Prompt

We try to use an OLAP Connection based on authentication type Prompt. This should cause a dialog to popup where the user can enter credentials for SAP BW. This works fine for Analysis for OLAP, but not in Web Intelligence and Design Studio.
In design studio the following message appears:
failed to connect to "BA1CLNT100"
Configuration of destination
customized_guid:FnTHdVPWmQ4AMLQAAD4XL4cAAFBWmWVp is incomplete:
Parameter user id missing: neither user nor user alias nor sso ticket nor certificate is specified.
Does anyone know if this feature is supported and what causes this error?

Hi,
Can you check the option "Disallow insecure incoming RFC connections" from CMC >> SAP Authentication and see if it helps.
-Ambarish-

Problem in CMC login with SAP authentication type

Hi,
We have installed the SAP Integration kit successfully for BO XI R2 & when I logon to CMC i am able to enable the SAP authentication and import the roles from the SAP BW system as well. But when I try to login into CMC using the 'Authentication type' as SAP it doesn't display the textboxes for entering System ID and Client details. Can you please tell me how to fix this?
Also I see that the CMC & Infoview authentication type drop down list are not the same. The CMC has the authentication types available as 'SAP,LDAP & Enterprise' where as Infoview has 'Enterprise, LDAP & AD'.
Is this an issue with the Plugins? do i need to do some settings on the Tomcat ?
Please help me out in this..
Thanks in advance!
Phani.

Thanks for your update Jac...yes thats correct. Also I had to include authPlugExt.properties file in the tomcat/shared/classes, which i did not include previously. The SAP infoview is working fine now.
Just one more question, in CMC login doesn't the SAP authentication require sap system & client id as its inputs? (in XI R2). I noticed that I was able to login with SAP user id's (without mentioning system details) , that have been added when I have imported the SAP roles to BO.

How to improve client handover and roaming between AP's

Improving client Handover and roaming between APs
There are a few standards and methodologies available to use to improve handover of clients between APs. Most are focused on VOIP technologies, but it must always be remembered that we cannot control the client Handover (especially with legacy clients) we can only encourage them. Some Standards and methods work well for some environments and some do not - test the recommendations extensively before implementing in a live Production environment. It must also be noted that all settings take effect immediately once applied, however from a client perspective it might need to re-associate for the changes to take effect client side.
As with everything else in IT, if a perfect method/solution existed there would only be one - try them all and keep the best.
The Standards and Definitions
802.11k
IEEE 802.11k allows a device to quickly identify nearby APs that are available for roaming. When the signal strength of the current AP weakens and the device needs to roam to a new AP, it will already know the best candidate AP with which to connect to.
802.11r
IEEE 802.11r specifies fast Basic Service Set (BSS) transitions between access points by redefining the security key negotiation protocol, allowing both the negotiation and requests for wireless resources to occur in parallel.
When a device roams from one AP to another on the same network, 802.11r streamlines the authentication process. BSS allows a devices to associate with APs more quickly. Coupled with 802.11k's ability to quickly identify the target AP, BSS's faster association method may enhance application performance.
Handoff Assist
The AP monitors the RSSI for every associated client. If the RSSI for a specific client falls below "low-rssi-threshold" and continues to fall for the "rssi-falloff-wait-time", then the AP will send a de-auth to the client.
The de-auth is meant to kick the client away from the current AP and get it to re-authenticate to a nearby AP. This will have the effect of helping a client handover between 2 APs.
BUT (Big But), if the client gets de-authed and takes a while to re-authenticate (if it even does re-authenticate automatically after a de-auth), then this will have the effect of destroying communication instead of helping it -- mostly found with legacy clients.
Remove Lower Transmit Rates
Removing lower transmit rates is a way to promote better roaming, BUT not all clients respond well, or even respond to it.
The practice is that the basic rates are a subset of the transmit rates. If you only want to allow speeds 9 and up, you would select only the transmit rates of 9 and up, and the basic rates of 9 and 11. If a legacy client expects the rates of 1 and 2 it will not connect.
Local Probe Threshold
Local probe Threshold prevents a client from connecting to an AP with a too low a signal - helps more with initial connection than roaming.
The local probe threshold parameter is not supposed to force clients to roam as soon as they pass near an access point with a good signal, but rather to NOT hold on to an access point with a weak signal (avoiding sticky clients).
PMK Caching
Defined by 802.11i and is a technique available for authentication between a single AP and a station. If a station has authenticated to an AP, roams away from that AP, and comes back, it does not need to perform a full authentication exchange. Only the 802.11i 4-way handshake is performed to establish transient encryption keys.
Opportunistic Key Caching (OKC)
Is a similar technique to PMK, but not defined by 802.11i, for authentication between multiple APs in a network where those APs are under common administrative control. An Aruba deployment with multiple APs under the control of a single controller is one such example. Using OKC, a station roaming to any AP in the network will not have to complete a full authentication exchange, but will instead just perform the 4-way handshake to establish transient encryption keys
Implementation and Configuration
802.11k
802.11k is configured in your VAP profile. Tick the option to “Advertise 802.11k”. There after set the Handover Trigger Feature Settings.
Tick the “Enable Handover Trigger feature” and then set RSSI threshold by specifying the -dBm level at what the hand over trigger should be sent to the client
802.11r
802.11r is configured under SSID of your VAP profile. Tick the option to “Advertise 802.11r”
HandofF Assist
Station Handoff Assist is enabled in RF Optimization under the RF Management section of AP configuration.
Tick the “Station Handoff Assist” option to enable it, next set the Low RSSI Threshold – the threshold determines above what level no deauth gets sent
Lower Transmit Rates
Transmit rates can be adjusted in the Advanced tab of SSID under your VAP profile.
Remember that the basic rates are a subset of the transmit rates. If you only want to allow speeds 9 and up, you would select only the transmit rates of 9 and up, and the basic rates of 9 and 11
Local Probe threshold
Local Probe threshold can be adjusted in the advanced tab of SSID under your VAP profile.
Depending on the density of your APs consider values between 20 and 40 -- 40 being aggressive in an AP dense area.
Deny Broadcast Probes
Denying Broadcast Probes can cause problems with Roaming especially if the SSID is hidden – leave option disabled.

Hi, thank you for the helpful guidance. I have a basic question, if the device roam from one AP to another AP with the same SSID. Is there a need of re-authentication given a) the network uses EAP based authentication; b) the network uses MAC address authentication. If there is no need of EAP re-authentication, how the 802.11 keys are moved to the new AP. Thank you very much if you could help me clarify my thought.

User domain\SPFservice is not authorized to perform request using authentication type Negotiate

Hi,
I have installed WAP/SPF in the same domain via express installation. The SPF domain service account is sysadmin on the SPF database. The SPF domain service account is running as identity in IIS application pool. I have registered SPF in
WAP via SPFcomputeraccount\LocalSPFaccount. The LocalSPFaccount is member of the 4 local groups created by the SPF setup. The domain SPF service account is member of the VMM administrators.
When a new tenant want to subscribe to a hosting plan I get an error "One or more errors occurred while contacting the underlying resource providers. The operation may be partially completed. Details: Failed to create subscription".
When I look in the eventviewer of the SPF server in ManagementODataService, I can see "User domain\SPFservice is not authorized to perform request using authentication type Negotiate".
SPF/VMM are both on the latest update rollup. The VMM console is also updated on the SPF server.
I can successfully reproduce the troubleshooting steps from http://blogs.technet.com/b/privatecloud/archive/2013/11/08/troubleshooting-windows-azure-pack-spf-amp-vmm.aspx.

Hi,
During the install it is also asking you to specify groups during the installation (4 x) Is the user you specified als spf runas account also member of those group in the AD?
So you have 4 groups created on the local box by the installation. But also 4 specified during the installation. Check if the account is member of those group(s) as well, reboot the spf and you should be up and running.
Best regards, Mark Scholman. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

How can I use authentication type in sending/receiving a message

Dear all,
I am building a mail client program. I have a problem: I don't know use javamail to authenticate to mail server in while send/receive messages. I know some authentication types as PLAIN, LOGIN, CRAM-MD5, DIGIT-MD5, NTLM and GSSAPI. and I tried use "mail.imap.sasl.mechanisms" property, but it do not work. Any suggestion is helpful for me. Thanks!

Thank for quick your reply,
I checked with Imap protocol to receive message. The mail server supported authentication type: Plain and Login. Below is code:
      Properties props = System.getProperties();
      String socketFactoryClass = "javax.net.SocketFactory";
      String host = account.getIncomingHost();
      int port = Integer.valueOf(account.getIncomingPort());
      String fallback = "mail.imap.socketFactory.fallback";
      String imapSocketFactoryClass = "mail.imap.socketFactory.class";
      String emailAddress = account.getIncomingUser();
      props.put("mail.mime.base64.ignoreerrors", "true");
      if (account.isIncomingSsl()) {
        MailSSLSocketFactory socketFactory = this.getSSLSocketFactory(host);
        if (account.getSecureAuthsIncoming().equalsIgnoreCase("starttls"))
          props.put("mail.imap.starttls.enable", true);
        else
          props.put("mail.imap.ssl.enable", "true");
        props.put("mail.imap.ssl.socketFactory", socketFactory);
        props.put("mail.imap.sasl.mechanisms", account.getAuthMechsIncoming());
      props.put(fallback, "false");
      props.put(imapSocketFactoryClass, socketFactoryClass);
      Session session = Session.getInstance(props, null);
      String protocolName = "imap";
      if (Utils.isGmailAccount(emailAddress))
        protocolName = imaps;
      IMAPStore imapStore = (IMAPStore) session.getStore(protocolName);
      try {
        imapStore.connect(host, port, emailAddress, account.getIncomingPassword());
      } catch (Exception e) {.....}account.getAuthMechsIncoming() return authentication types, this instance is Login or Plain(as I tested). By the way, I have a problem how to check authentication types supported by server(as Evolution Mail on Ubuntu has)?. sorry for my English. Thank for your consider time.

Wireless Client Authentication issues when roaming Access Points (Local)

I have a Cisco 5508 with Software version 7.4.121.0 and Field Recovery 7.6.101.1.
There are a handful of clients that when roaming between AP's with the same SSID that get an authentication issue and have to restart the wireless to get back on.
From Cisco ISE
Event
5400 Authentication failed
Failure Reason
11514 Unexpectedly received empty TLS message; treating as a rejection by the client
Resolution
Ensure that the client's supplicant does not have any known compatibility issues and that it is properly configured. Also ensure that the ISE server certificate is trusted by the client, by configuring the supplicant with the CA certificate that signed the ISE server certificate. It is strongly recommended to not disable the server certificate validation on the client!
Root cause
While trying to negotiate a TLS handshake with the client, ISE expected to receive a non-empty TLS message or TLS alert message, but instead received an empty TLS message. This could be due to an inconformity in the implementation of the protocol between ISE and the supplicant. For example, it is a known issue that the XP supplicant sends an empty TLS message instead of a non-empty TLS alert message. It might also involve the supplicant not trusting the ISE server certificate for some reason. ISE treated the unexpected message as a sign that the client rejected the tunnel establishment.
I am having a hard time figuring out what is causing this. My assumption is if there were a problem with the Controller or AP configurations then it would happen to everyone. My further assumption is if the client had a problem with their laptop (windows 7) then why does work at other times? So I have checked and the ISE certificate is trusted by client.
Is something happening that the previous access point is holding on to the mac and the return authentication traffic is going to the old AP instead of the new one or something like that which is corrupting the data?
I also had this from Splunk for the same client:
Mar 5 13:44:51 usstlz-piseps01 CISE_Failed_Attempts 0014809622 1 0 2015-03-05 13:44:51.952 +00:00 0865003824 5435 NOTICE RADIUS: NAS conducted several failed authentications of the same scenario
FailureReason="12929 NAS sends RADIUS accounting update messages too frequently"
Any help on this would be appreciated. These error messages give me an idea but doesn't give me the exact answer to why the problem occurred and what needs to be done to fix it.
Thanks

Further detail From ISE for the failure:
11001
Received RADIUS Access-Request
11017
RADIUS created a new session
15049
Evaluating Policy Group
15008
Evaluating Service Selection Policy
15048
Queried PIP
15048
Queried PIP
15004
Matched rule
15048
Queried PIP
15048
Queried PIP
15004
Matched rule
11507
Extracted EAP-Response/Identity
12500
Prepared EAP-Request proposing EAP-TLS with challenge
11006
Returned RADIUS Access-Challenge
11001
Received RADIUS Access-Request
11018
RADIUS is re-using an existing session
12301
Extracted EAP-Response/NAK requesting to use PEAP instead
12300
Prepared EAP-Request proposing PEAP with challenge
11006
Returned RADIUS Access-Challenge
11001
Received RADIUS Access-Request
11018
RADIUS is re-using an existing session
12302
Extracted EAP-Response containing PEAP challenge-response and accepting PEAP as negotiated
12318
Successfully negotiated PEAP version 0
12800
Extracted first TLS record; TLS handshake started
12805
Extracted TLS ClientHello message
12806
Prepared TLS ServerHello message
12807
Prepared TLS Certificate message
12810
Prepared TLS ServerDone message
12305
Prepared EAP-Request with another PEAP challenge
11006
Returned RADIUS Access-Challenge
11001
Received RADIUS Access-Request
11018
RADIUS is re-using an existing session
12304
Extracted EAP-Response containing PEAP challenge-response
12305
Prepared EAP-Request with another PEAP challenge
11006
Returned RADIUS Access-Challenge
11001
Received RADIUS Access-Request
11018
RADIUS is re-using an existing session
12304
Extracted EAP-Response containing PEAP challenge-response
12305
Prepared EAP-Request with another PEAP challenge
11006
Returned RADIUS Access-Challenge
11001
Received RADIUS Access-Request
11018
RADIUS is re-using an existing session
12304
Extracted EAP-Response containing PEAP challenge-response
12305
Prepared EAP-Request with another PEAP challenge
11006
Returned RADIUS Access-Challenge
11001
Received RADIUS Access-Request
11018
RADIUS is re-using an existing session
12304
Extracted EAP-Response containing PEAP challenge-response
12305
Prepared EAP-Request with another PEAP challenge
11006
Returned RADIUS Access-Challenge
11001
Received RADIUS Access-Request
11018
RADIUS is re-using an existing session
12304
Extracted EAP-Response containing PEAP challenge-response
12305
Prepared EAP-Request with another PEAP challenge
11006
Returned RADIUS Access-Challenge
11001
Received RADIUS Access-Request
11018
RADIUS is re-using an existing session
12304
Extracted EAP-Response containing PEAP challenge-response
12305
Prepared EAP-Request with another PEAP challenge
11006
Returned RADIUS Access-Challenge
11001
Received RADIUS Access-Request
11018
RADIUS is re-using an existing session
12304
Extracted EAP-Response containing PEAP challenge-response
11514
Unexpectedly received empty TLS message; treating as a rejection by the client
12512
Treat the unexpected TLS acknowledge message as a rejection from the client
11504
Prepared EAP-Failure
11003
Returned RADIUS Access-Reject

"Authentication Type" greyed out in Advanced Wireless Settings (WRT54G)

I wish to change my Authentication Type from Auto to Shared Key in my Wireless -> Advanced Wireless Settings section of my web-based admin utility. However, it's been greyed out for some reason.
I understand that the Shared Key mode is more secure than the Auto mode, therefore I wish to change it. Would anyone happen to know as to why this would be greyed out like this and how I can fix it so that I can have access to the options? I'm using WRT54G V.6 with firmware v.1.01.1 (the latest one from linksys). TIA.

I think I figured it out. I'm currently using WPA Personal mode and as I understand it, only WEP mode applies to whether you're using an Open System or Shared Key. Can someone please confirm this for me? TIA.

Users authentication type problem

Dears,
I'm working on ISE 1.1 version, am facing the following problem:
When the user turn on the PC , he can access to the network via Dot1x , but when the PC go to the sleeping mode , the Dot1x timed out , and the authentication type become mab , so that the user access as guest , and he need to restart the dot1x service manually to get the access again .
Below is a port switch configuration:
interface FastEthernet0/X
switchport access vlan 22
switchport mode access
switchport voice vlan 110
authentication port-control auto
mab
dot1x pae authenticator
spanning-tree portfast
any idea? please advice.
Thank you in advance
Zahi

A suggestion since this is not something I can test
Should be able to distinguish the case of guest access from employee access since in the case of guest the endpoint will not exist in the database and create authoirzations accordingly
Can distinguish the case of whether endpoint was found using the following attribute in the authorization policy
Attribute: NetworkAccess.AuthentictionStatus
value: UnknownUser indicates that record was not found during the authentication

Having thousands of Host-Named Site Collections - which authentication type?

So Microsoft seems to state the claims + Host-Named Site Collection (HNSC) approach is the way to go forward.
Assuming we have thousands of site collections, and we don't want to go with good ol' NTLM authentication as our claim authentication type, then how should we authenticate?
Both Kerberos and SAML would be a nightmare to manage, since for Kerberos we need to register a Service Principal Name (SPN) per HNSC. For SAML we would end up in a similar situation, since this would require us to configure a relying party
+ realm for every HNSC.

Please see the documentation on using managed paths with host named site collections.
http://technet.microsoft.com/en-us/library/cc288637(v=office.14).aspx#section5
You would be very unlikely to have thousands of individual host names, I would never recommend such an architecture to a customer. Instead, you are much more likely to use managed paths (/sites/, /personal/, etc) in combination with host names, significantly
reducing the number of individual host names while still allowing you to easily scale to thousands of site collections.
In Office 365, each tenant is provisioned with 3 top-level host names (<tenant>.sharepoint.com, <tenant>-public.sharepoint.com, and <tenant>-my.sharepoint.com), all subsequent site collections are provisioned using managed paths.
Note that this is not really a question particular to HNSC. If you decide to not use host-named site collections but want to use individual host names using web applications, you get far less. According to our Software Boundaries and
Limits document, you get maximum 20 web applications per farm with a maximum 5 AAMs per web application, yielding a maximum 100 individual host names.
http://technet.microsoft.com/en-us/library/cc262787.aspx
While you can achieve more host names using HNSC, I would strongly discourage this design and instead seek to leverage managed paths.
Kirk Evans
Architect, Azure Modern Apps Center of Excellence
Microsoft Corporation
Microsoft Certified Master, SharePoint 2010
http://blogs.msdn.com/kaevans

Setting Defualt Authentication type to Enterprise in Full Client - strange

Hi Folks,
I am having issue setting up default authentication type in full client.
My users here use Desktop Intelligence for their reporting. We have configured Windows AD authentication for them and they are logging to one of the server via Citrix where BO Client is installed. When users select Windows AD from the authentication type, for the first time it works well, because, they dont have to enter username or password, as they are logging thru Citrix to the server with their Windows AD account. Now here is what happens, when second time they go in the server, their default type is set to Windows AD as they login to DeskI using AD last time, but this time, the OK button is blurred and to my understanding it becomes active if you enter username or password, which in my situation, they have dont have to.
So they select Windows AD from the drop down button and then the OK button is enabled. This is not right as they are already in Windows AD mode. So I thought to make the defualt authentication mode to Enterprise, no matter whatever they login lastly. This way they will have to select Windows AD and the problem will go away. Or if someone knows how to resolve my situation, please advice. Otherwise, please help me how and where can I set the autheication type to Enterprise by defualt for full client. I have only client products installed on this particular server.
Thanks a lot,
Bhaumik
BOXIR2 SP2 full version, Citrix

The ok button thing was a bug fixed in SP3. Now beware SP3 and above SP's client version have another bug which breaks all clients using AD/LDAP fixed in FP3.3. The server version of the SP does not have that bug. If you fix the bug you will not have to set the enterprise type.
It's by design to remember that last login (that may be something you can stop but I never tried and don't know how to).
Regards,
Tim

History Attributes when using Custom Authentication Type

assigned all History Attributes (in the Entity Object Editor) to my audit columns.
During run time, I find only Created By is assigned the SYSDATE, and Created On, Modified On, and Modified By are null.
I am using Custom Authentication Type.
I have read that the History Attributes only work the the JAAS authentication type. Appreciate any one confirming this.
Also, how do you implement History Attributes if you are using the Custom Authentication Type? Do you need to write Java code?
Thanks.
John

Hi,
confirmed it only works with container managed authentication performed through JAZN. You can't use this with custom security as otherwise this feature could be overwritten. Still you can provide your own implementation:
- create a custom table
- use the setAttr method on the RowImpl class of a VO to store the username
Frank

SMTPAuthenticationException:504 5.7.4 Unrecognized authentication type

Hi Folks,
we have a 3rd party system that wants to send automated emails externally, I have setup a new receive connector on our cashub servers just to allow this server to be able to use our exchange as a relay, I've checked all the forums about how to do it and
followed all the recommended instructions.
we've been testing the 3rd party system to see in the emails get sent correctly and they are not, when I check the logs I get the below , can anyone suggest anything I haven't already tried?
thanks in advance.
Owen.
error message 1:
Exception information:
--------------------------------------------------1
Quiksoft.EasyMail.SMTP.SMTPAuthenticationException:504 5.7.4 Unrecognized authentication type
   at Quiksoft.EasyMail.SMTP.SMTP.?(String A_0, EmailMessage A_1, ? A_2, SMTPQueueType A_3, Boolean A_4)
   at Quiksoft.EasyMail.SMTP.SMTP.Send(EmailMessage MessageObj)
   at Odyssey.Workflow.WorkflowEmailActionNode.SendEmail(String to, String cc, String from, String bcc, String subject, String body, MailFormat bodyFormat, String[] attachments, Boolean deleteAttachmentsAfterSend, String smtpServerName, Boolean isAuth,
Int32 smtpPort, String smtpLogin, String smtpPassword)
   at Odyssey.Workflow.WorkflowEmailActionNode.SendEmail(String to, String cc, String from, String bcc, String subject, String body, MailFormat bodyFormat, String attachment, Boolean deleteAttachmentsAfterSend, String smtpServer, Boolean isAuth, Int32
smtpPort, String smtpLogin, String smtpPassword)
   at Odyssey.Workflow.Generated.LOCKEDResourceNotificationEmailCallAssigned_v43.EmailExternal_Logic()
error message 2:
Workflow Worker Action failed
Exception information:
--------------------------------------------------1
System.InvalidOperationException:The worker experienced an error in 'Run'.
   at Odyssey.Workflow.Actions.WorkflowWorkerAction.RunWorker(WorkflowDom dom, WorkflowWorker worker, AuditWriter& writer)
   at Odyssey.Workflow.Actions.WorkflowWorkerAction.Run(IActionExecutionContext context)
--------------------------------------------------2
Quiksoft.EasyMail.SMTP.SMTPAuthenticationException:504 5.7.4 Unrecognized authentication type
   at Quiksoft.EasyMail.SMTP.SMTP.ᜀ(String A_0, EmailMessage A_1, ᜄ A_2, SMTPQueueType A_3, Boolean A_4)
   at Quiksoft.EasyMail.SMTP.SMTP.Send(EmailMessage MessageObj)
   at Odyssey.Workflow.WorkflowEmailActionNode.SendEmail(String to, String cc, String from, String bcc, String subject, String body, MailFormat bodyFormat, String[] attachments, Boolean deleteAttachmentsAfterSend, String smtpServerName, Boolean
isAuth, Int32 smtpPort, String smtpLogin, String smtpPassword)
   at Odyssey.Workflow.WorkflowEmailActionNode.SendEmail(String to, String cc, String from, String bcc, String subject, String body, MailFormat bodyFormat, String attachment, Boolean deleteAttachmentsAfterSend, String smtpServer, Boolean isAuth,
Int32 smtpPort, String smtpLogin, String smtpPassword)
   at Odyssey.Workflow.Generated.LOCKEDResourceNotificationEmailCallAssigned_v44.EmailExternal_Logic()
   at Odyssey.Workflow.Generated.LOCKEDResourceNotificationEmailCallAssigned_v44.IsExternalResource_Navigate()
   at Odyssey.Workflow.Generated.LOCKEDResourceNotificationEmailCallAssigned_v44.HasAssignmentType_Navigate()
   at Odyssey.Workflow.Generated.LOCKEDResourceNotificationEmailCallAssigned_v44.IsitavalidEmailAddress_Navigate()
   at Odyssey.Workflow.Generated.LOCKEDResourceNotificationEmailCallAssigned_v44.IsBREAKDOWNTask_Navigate()
   at Odyssey.Workflow.Generated.LOCKEDResourceNotificationEmailCallAssigned_v44.Run()
   at Odyssey.Workflow.Actions.WorkflowWorkerAction.RunWorker(WorkflowDom dom, WorkflowWorker worker, AuditWriter& writer)
error message 3:
Entity Audit Error Message
Entity Type: Odyssey.Workflow.WorkflowDom
Entity id: 34
Email External: Unexpected exception
Exception information:
--------------------------------------------------1
Quiksoft.EasyMail.SMTP.SMTPAuthenticationException:504 5.7.4 Unrecognized authentication type
   at Quiksoft.EasyMail.SMTP.SMTP.ᜀ(String A_0, EmailMessage A_1, ᜄ A_2, SMTPQueueType A_3, Boolean A_4)
   at Quiksoft.EasyMail.SMTP.SMTP.Send(EmailMessage MessageObj)
   at Odyssey.Workflow.WorkflowEmailActionNode.SendEmail(String to, String cc, String from, String bcc, String subject, String body, MailFormat bodyFormat, String[] attachments, Boolean deleteAttachmentsAfterSend, String smtpServerName, Boolean
isAuth, Int32 smtpPort, String smtpLogin, String smtpPassword)
   at Odyssey.Workflow.WorkflowEmailActionNode.SendEmail(String to, String cc, String from, String bcc, String subject, String body, MailFormat bodyFormat, String attachment, Boolean deleteAttachmentsAfterSend, String smtpServer, Boolean isAuth,
Int32 smtpPort, String smtpLogin, String smtpPassword)
   at Odyssey.Workflow.Generated.LOCKEDResourceNotificationEmailCallAssigned_v44.EmailExternal_Logic()
hope these errors help!

Hi,
Based on my knowledge, Exchange 2010 does not allow inbound unauthenticated mail by default.
I suggest configuring the default receive connector to allow "anonymous".
Found a similar thread for your reference:
Error in establishing SMTP connection, Error: 504 5.7.4 Unrecognized authentication type
http://social.technet.microsoft.com/Forums/en-US/93ad411a-0da2-4494-a45e-8cbb793aeca9/error-in-establishing-smtp-connection-error-504-574-unrecognized-authentication-type?forum=exchange2010
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Authentication type for cl_http_client= create_by_url

Hi All,
I am trying to understand how to set authentication type
for "cl_http_client=>create_by_url".
It is currently defaulting to client certificate.
ICM log: "auth_type=3 (USE_CLIENT_CERT)) "
I need to set to no authentication as server requires password/user as url parms.
If I use an RFC dest I can set to "No logon" but then I cannot append user/pass to the url.
Any help appeciated
Thanks in advance
Allan

you can just use the following code sample.
concatenate
'http://<siteaddress>/<loginpage>?<useridparameternameincalledsystem>='
'useridtobepassedtocalledsystem' '&<passwordfilenameincalledsystem>=<password>' into wf_String .
call method cl_http_client=>create_by_url
    exporting
      url                = wf_string
    importing
      client             = http_client
    exceptions
      argument_not_found = 1
      plugin_not_active = 2
      internal_error     = 3
      others             = 4.
where did you find that its using SSL?
in case if the called url required ssl certificate, then you can to download the certificate from that system and load it in ABAP system and use the sslid to pass it to create_by_url method.
Regards
Raja

Cannot modify Authentication Type setting

I am running the WRT54G (v.6) with firmware v1.0.0.9. I am unable to modify the Authentication Type setting in the utility because the box is grayed-out. It is currently set to Auto (by deafult). Is the setting correct since I am using WPA2 Personal? I do not even know what the other options are since I cannot modify the setting. Thanks.
Wireless->Advanced Wireless Settings->Authentication Type

Hi… This authentication type is different then wireless security mode i.e. either WEP or WPA or WPA2. If want to what is your wireless security mode then go to wireless -> wireless security -> security mode, here you have an option to select the security mode. Select appropriate security mode supported by your OS and Wireless adapters on wireless computers.

Authentication types and roaming

Similar Messages

Maybe you are looking for