] On Behalf Of Randy Evans
Sent: Wednesday, June 29, 2011 7:08 PM
To: arslist@ARSLIST.ORG
Subject: 7.6.04 Mid-Tier and SSO.
I've got the white paper that describes SSO on the Mid-Tier and has 2
examples of how to authenticate, one in C++ and the other In Java. In
the Java example it uses two imports
: 7.6.04 Mid-Tier and SSO.
I've got the white paper that describes SSO on the Mid-Tier and has 2
examples of how to authenticate, one in C++ and the other In Java. In
the Java example it uses two imports
import com.remedy.arsys.session.Authenticator;
import
] On Behalf Of Randy Evans
Sent: 30 June 2011 12:16
To: arslist@ARSLIST.ORG
Subject: Re: 7.6.04 Mid-Tier and SSO.
What were trying to accomplish is the user opens up the web browser and
either by favorite or link goes directly to our Mid-Tier and doesn't
have to login. Currently all our Remedy
.
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Danny Kellett
Sent: Thursday, June 30, 2011 05:07 AM
To: arslist@ARSLIST.ORG
Subject: Re: 7.6.04 Mid-Tier and SSO.
No, you have to login to AtriumSSO first. So instead of logging
: Thursday, June 30, 2011 05:07 AM
To: arslist@ARSLIST.ORG
Subject: Re: 7.6.04 Mid-Tier and SSO.
No, you have to login to AtriumSSO first. So instead of logging into
midtier, you login to AtriumSSO.
Also, when it times out, you will have to do it again.
Your options are as follows: A product
Axton
To fully support SPNEGO, one requires both Kerberos+NTLMv2. To my knowledge,
there is no complete implementation outside of SSO Plugin, in and out of the
BMC market, let alone an implementation with AD failover support and all the
other features that serious clients demand from a
I have web applications that are behind https that only support spnego in an
AD environment. We are able to use a series of AD servers to service the
requests, from both the client and server side. We use basic authentication
as a fail back in the event SPNEGO fails. This prompts the user for
Axton,
We use basic authentication as a fail back in the event SPNEGO fails.
So you're missing SSO for a number of browsers that decide to send an NTLM
token, or an NTLM token buried in an SPNEGO token. That's quite a large piece
of functionality for large BMC clients who may have 20,000+
Actually I wish we *could* fall back to Basic Auth instead of NTLM with
our IIS/Negotiate SSO implementation. Android currently does not
support NTLM, so there is no way to authenticate to our Remedy or
Sharepoint site. Any thoughts?
Brien
On 6/30/2011 1:58 PM, John Baker wrote:
Axton,
This behavior can be corrected through the browsers configuration. There
are tools that can even manage such configurations, enterprise wide. For
IE, you place the domain in your intranet sites (i.e., *.domain.com). For
FireFox, you set the following parameters:
I've got the white paper that describes SSO on the Mid-Tier and has 2
examples of how to authenticate, one in C++ and the other In Java. In
the Java example it uses two imports
import com.remedy.arsys.session.Authenticator;
import com.remedy.arsys.session.UserCredentials;
which JAR are
relations representative for BMC Software, Inc.
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Randy Evans
Sent: Wednesday, June 29, 2011 04:08 PM
To: arslist@ARSLIST.ORG
Subject: 7.6.04 Mid-Tier and SSO.
I've got the white
Use the jars provided with the mid-tier in the WEB-INF/lib directory. This
includes all the Remedy API jars in addition to the mid-tier specific jars.
Axton
On Wed, Jun 29, 2011 at 6:07 PM, Randy Evans lilbear63_2...@yahoo.comwrote:
I've got the white paper that describes SSO on the Mid-Tier
13 matches
Mail list logo
