Unable to authenticate with Ticket Toolkit

[Former Member]

I'm having trouble with the Ticketing Toolkit.

(in a previous thread I was having trouble obtaining the MYSAPSSO2 cookie ... that is thankfully resolved)

I am now able to see the cookie but for some reason the IsAuthenticated flag isn't set when I run the app by clicking "Preview" from the associated iview. Consiquently Identity.Name isn't set + The Authentication Type is blank as well.

I've played around with the web.config as well as the virtual directory on IIS; changing the Authentication Mode from "Windows" to "None", enabling Windows authentication and disabling anonymous user authentication .... and every permutation you can think of .... nothing seems to work.

One interesting note is that the wpsso_v3.dll doesn't seem to be called ... I tried renaming it just to see if it generated an error and it didn't make any difference.

Also, I had to physically make a reference to the assembly SAP.web.security for the app to build. The artcle on the toolkit didn't indicate that I would need to do that and I would have thought the registration in the web.config would have taken care of that.

My web.config is as follows:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<configSections>
 <sectionGroup name="system.web">
   <section name="MySAPSSO2" 
     type="SAP.Web.Security.MySapSso2SectionHandler, SAP.Web.Security, Culture=neutral, PublicKeyToken=50436dca5c7f7d23, Version=1.0.0.0"/>
   </sectionGroup>
</configSections>
    
  <system.web>
    <httpModules>
   <add type="SAP.Web.Security.MySapSso2AuthenticationModule, SAP.Web.Security, Culture=neutral, PublicKeyToken=50436dca5c7f7d23, Version=1.0.0.0" name="MySAPSSO2"/>
  </httpModules>
                
  <MySAPSSO2 PseFilePath="C:InetpubwwwrootSSO Ticket TestpseFilesverify.pse" />

    <!--  DYNAMIC DEBUG COMPILATION
          Set compilation debug="true" to enable ASPX debugging.  Otherwise, setting this value to
          false will improve runtime performance of this application. 
          Set compilation debug="true" to insert debugging symbols (.pdb information)
          into the compiled page. Because this creates a larger file that executes
          more slowly, you should set this value to true only when debugging and to
          false at all other times. For more information, refer to the documentation about
          debugging ASP.NET files.
    -->
    <compilation 
         defaultLanguage="c#"
         debug="true"
    />

    <!--  CUSTOM ERROR MESSAGES
          Set customErrors mode="On" or "RemoteOnly" to enable custom error messages, "Off" to disable. 
          Add <error> tags for each of the errors you want to handle.

          "On" Always display custom (friendly) messages.
          "Off" Always display detailed ASP.NET error information.
          "RemoteOnly" Display custom (friendly) messages only to users not running 
           on the local Web server. This setting is recommended for security purposes, so 
           that you do not display application detail information to remote clients.
    -->
    <customErrors 
    mode="RemoteOnly" 
    /> 

    <!--  AUTHENTICATION 
          This section sets the authentication policies of the application. Possible modes are "Windows", 
          "Forms", "Passport" and "None"

          "None" No authentication is performed. 
          "Windows" IIS performs authentication (Basic, Digest, or Integrated Windows) according to 
           its settings for the application. Anonymous access must be disabled in IIS. 
          "Forms" You provide a custom form (Web page) for users to enter their credentials, and then 
           you authenticate them in your application. A user credential token is stored in a cookie.
          "Passport" Authentication is performed via a centralized authentication service provided
           by Microsoft that offers a single logon and core profile services for member sites.
    -->
    
   <authentication mode="Windows" /> 


	
	<!--  AUTHORIZATION 
          This section sets the authorization policies of the application. You can allow or deny access
          to application resources by user or role. Wildcards: "*" mean everyone, "?" means anonymous 
          (unauthenticated) users.
    -->

    <authorization>
		
      <allow users="*" />      <!-- Allow all users -->
            <!--  <allow     users="[comma separated list of users]"
                             roles="[comma separated list of roles]"/>
                  <deny      users="[comma separated list of users]"
                             roles="[comma separated list of roles]"/>
            -->
      <!-- <deny users="?" /> --> 
    </authorization>

    <!--  APPLICATION-LEVEL TRACE LOGGING
          Application-level tracing enables trace log output for every page within an application. 
          Set trace enabled="true" to enable application trace logging.  If pageOutput="true", the
          trace information will be displayed at the bottom of each page.  Otherwise, you can view the 
          application trace log by browsing the "trace.axd" page from your web application
          root. 
    -->
    <trace
        enabled="false"
        requestLimit="10"
        pageOutput="false"
        traceMode="SortByTime"
		localOnly="true"
    />

    <!--  SESSION STATE SETTINGS
          By default ASP.NET uses cookies to identify which requests belong to a particular session. 
          If cookies are not available, a session can be tracked by adding a session identifier to the URL. 
          To disable cookies, set sessionState cookieless="true".
    -->
    <sessionState 
            mode="InProc"
            stateConnectionString="tcpip=127.0.0.1:42424"
            sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes"
            cookieless="false" 
            timeout="20" 
    />

    <!--  GLOBALIZATION
          This section sets the globalization settings of the application. 
    -->
    <globalization 
            requestEncoding="utf-8" 
            responseEncoding="utf-8" 
   />
   
 </system.web>

</configuration>

I am afraid that I am running out of ideas ... anyone have some suggestions?

-Sheldon

[Former Member]

Turns out that this was another variation on on Mark Dohrmann's post "Problem's known with NW2004s SP11 and Ticket Toolkit"

just had to convert the ticket string and feed it back into the cookie before passing to the toolkit.

ie.

this.Request.Cookies["MYSAPSSO2"].Value = HttpUtility.UrlDecode(this.Request.Cookies["MYSAPSSO2"].Value);