I'm attempting to add External Authentication to my company's Remedy
application. If anyone can give me general advice or has any incite into
the problems that I have encountered I would appreciate it. We are using
Action Request System 4.5 under Windows 2000.

The problems that I have encountered are as follows.

1) I can't configure the system to use External Authentication. The
programmer's guide says to open the Server Information window in Remedy
Administrator and choose the Configuration tab and select Authenticate
Unregistered Users. The problem is that I don't see this option.

2) I was searching the knowledge base and I found the following comments
about using the Authenticate Unregistered Users option which is required for
external authentication. Of course the programmer's guide and the rest of
the documentation that I have read make no mention of this.

The NT Server team does not recommend using the Authenticate
Unregistered Users feature for NT. It was primarily designed for UNIX
servers. Per the 4.5 Workflow Administrator guide on page 2.36 it is
disabled by default on NT and enabled by default on UNIX. They recommend
unchecking Authenticate Ungregistered Users and also viewing the ar.cfg file
and making sure an entry of the type Use-Password-File: T does not
exist. If it does, then delete the line and save the file. You should be
able to use Cross-Reference Blank password, and you can also give Demo (or
whichever user is the Admin) in SHR:ApplicationSettings a password as long
as the user has a password in the User form. You can also set this admin to
have no password in User and in SHR:ApplicationSettings. So long as this
user had a user account in NT, the Cross Reference Blank password should
still allow rappsvc to login. So to make a long story short, there is
apparently a conflict with running the Authenticate Unregistered Users on NT
and starting up the Remedy Application Service. With this option turned on
in NT, the AR Server is unable to authenticate the owner of the rappsvc as
being an admin. It therefore connects this user as a guest user, and the
rights are insufficient to start the service.


3) In building the sample program that was provided I ran into several
problems. In the end I got the executable created but the link process had
a warning. I am using Visual Studio 6.0.

I attempted to compile and link via the command line. I attempted
this twice with the following two commands:
o nmake areasamp.mak
o nmake /f "areasamp.mak" CFG="AREASAMP - WIN32 RELEASE"
For both I got the following error message:
Microsoft (R) Program Maintenance Utility Version
6.00.8168.0
Copyright (C) Microsoft Corp 1988-1998. All rights reserved.

Invalid configuration "AREASAMP - WIN32 RELEASE" specified.
You can specify a configuration when running NMAKE
by defining the macro CFG on the command line. For example:

NMAKE /f "areasamp.mak" CFG="AREASAMP - WIN32 RELEASE"

Possible choices for configuration are:

"areasamp - Win32 Release" (based on "Win32 (x86) Console
Application")

areasamp.mak(18) : fatal error U1050: An invalid
configuration is specified.
Stop.

I created a Visual Studio work space from the make file. When I
first linked it, I got an error from the link process that it could not find
the library file aread.lib. The area api package does not come with a
library by this name. It does have a library named area.lib which is the
one listed in the makefile. I modified Visual Studio to use area.lib
instead of aread.lib and the link succeeded but there was the following
warning:
MSVCRTD.lib(cinitexe.obj) : warning LNK4098: defaultlib
"msvcrt.lib" conflicts with use of other libs; use /NODEFAULTLIB:library
When I used the /NODEFAULTLIB link option the link fails with the
following error message:
Linking...
areasamp.obj : error LNK2001: unresolved external symbol
_strcmp
areasamp.obj : error LNK2001: unresolved external symbol
__imp__malloc
areasamp.obj : error LNK2001: unresolved external symbol
__imp__free
LINK : error LNK2001: unresolved external symbol
_mainCRTStartup
Debug/areasamp.exe : fatal error LNK1120: 4 unresolved
externals
Error executing link.exe.

_____________________________