I'm trying to create a simple hack on the DNN authentication service to provide a single point of login for multiple portals - that is, you login from one page, and it redirects you to your portal.  I've got code that I believe will do this, however I can't figure out how to set up an installable package.  The errors on Authentication Module installation are less than helpful ("Installation failed, see below" "Installation failed").

The process I used was to simply clone the AuthenticationServices/DNN directory, and add my hacks in.  I suspect that there's something somewhere else that I need to touch, but I'm not sure what - the OpenID and LiveID have a .dll as well, which there's no indication from where they come.  There also seem to be .resource files, too, that I have the same situation with: I don't know what they are, where they come from, or what they do.

Any help would be appreciated.

Thanks,

Mike

Ok, let's see if I understand the architecture and all that, now:

• The user sees an Authentication Service module, which deals with the login UI behaviour.  As I want to put in a URL redirect after login, this is where that should go, yes?
• The Authentication Services use an underlying Authentication Provider which deals with actually validating whether users are allowed in.  The AS should not, itself, do any validating.

• DNN is expecting that any Authentication Service module comes with its own Authentication Provider?  Thus, if I'm only using the DNN default stuff, I run into issues as I've only got the frontend changed.
• The .dnn file uses a different syntax for Auth_Service packages than for basic DNN modules - this further reinforces that they're considered separate things (I managed to get my DNN_Global working as a module, for a definition of "working" that involves showing up, but doing nothing :p)

So, further questions: if DNN is expecting an Auth Provider with the frontend, where can I turn that off in the code?  Second, what should a valid .dnn file look like?  Here's what I've got:

<dotnetnuke type="Package" version="4.0">
  <packages>
    <package name="DNN_Global" type="Auth_System" version="01.00.00">
      <friendlyname>Global Authentication Project</friendlyname>
      <description/>
      <vendor>
        <companyName>X</companyName>
      </vendor>
      <dependencies />
      <components>
        <component type="AuthenticationSystem">
          <authenticationService>
            <type>DNN_Global</type>
            <settingsControlSrc>DesktopModules/AuthenticationServices/DNN_Global/Settings.ascx</settingsControlSrc>
            <loginControlSrc>DesktopModules/AuthenticationServices/DNN_Global/Login.ascx</loginControlSrc>
            <logoffControlSrc/>
          </authenticationService>
        </component>
        <component type="File">
          <files>
            <basePath>DesktopModules/AuthenticationServices/DNN_Global</basePath>
            <file>
              <path>App_LocalResources</path>
              <name>Login.ascx.resx</name>
            </file>
            <file>
              <path>App_LocalResources</path>
              <name>Settings.ascx.resx</name>
            </file>
            <file>
              <name>Login.ascx</name>
            </file>
            <file>
              <name>Login.ascx.vb</name>
            </file>
            <file>
              <name>Settings.ascx</name>
            </file>
            <file>
              <name>Settings.ascx.vb</name>
            </file>
          </files>
        </component>
      </components>
    </package>
  </packages>
</dotnetnuke>

And my final question is: what should be contained within the installation zip file?

Thanks again,

Mike

Found at least one critical error, and I'm going to fix it now: the license column of the Packages table is declared NOT NULL.  I can understand that being the case - no license normally doesn't make sense.  I don't know if there's any more errors with my package yet.

I would suggest when the package is validated before showing the "accept license" screen, if there isn't a license then there should be an error message shown.  The other option is to remove the "NOT NULL" or just insert '' when there's no license file.

Thanks again,

Mike