When using the Letter Moudle, we are able to create and merge letters in to our IMIS System locally at each work station.  However when sharing these form letters between users, only the originating user is able to use the form letter.  The 3 or 4 additional users are unable to use the form letter.  Has anyone solved this issue?

Ralph

I have modified the Main Tables, Search and Report Fields parameters in Report Specs for a Word letter.

When a user wants to copy and modify this letter, they do "Save As" within the iMIS letter system. When iMIS creates the new entry in Report_Desc then it takes the Main Tables information from the letter being copied. However, it takes the Search and Report Fields information from elsewhere in iMIS.

I have found where the Report Fields value comes from; it is in System_Params where ParameterName = 'FR_Control.WordMergeFields' (FR for fundraising).

However, I cannot tack down where the Search value is being pulled from.

I have been asked by an AE whether it would be possible for us to create a custom login page for iMIS that allowed users to login to iMIS using either their Facebook, google or twitter credentials, 

All these apps now use OAuth 2 - which I have been reading about here developers.facebook.com/docs/authentication/.  and here oauth.net/2/

We would like our members to login into our association website but be instantly logged in our public view system without logging in twice.My concern is that we do not have access to the source code within the public view system, only the compiled version.

So my question is there any way technically that this can happen without touching the public view system.

Our company has this website developed in-house many years ago now. It basically is for our sales team to keep track of their retention meetings and such It doesn’t really tie too much into the iMIS database, except I think it grabs member data, such as company, phone, etc. The login in part of this website uses a hash to read the user password. I’m not sure for what reason, but it seems it calls a couple ASI related DLLs called ASIUtil.CCrypto, and OmniHash.

We have a number of custom administrative tools that we're moving into a separate, internal-only, Web site.

Currently the applications use their own ASP.NET authentication tables, but it would be ideal to leverage the information contained within iMIS directly. Not single-sign on, but sign-on validating against iMIS.

Since we've already got the site setup, I wanted an addition that would impact the site as little as possible. For that reason, I decided to first look at the Membership Web services - methods returned by the service and some detail on http://www.imiscommunity.com/use_the_membership_web_service as well - and see if we could successfully leverage that.

I have created a login page consuming the MembershipWebservice and invoking the LoginUserAndProvideCookies method.  It is giving me back 2 cookies:
 
•         ASP.NET_SessionId
•         Login
 
I create the cookies and send  the user to the mycart.aspx page.  The page is asking me to login.  After I login using the iMIS interface, I see that many more cookies have been created. 
 
I don’t want the user to have to log in twice.  Are these two cookies the only ones I need to create in order for the user to navigate the iMIS public site?
 

Has anyone created a page that will allow someone to create a username and password and log them in to WCM at the same time? 

We have a page using iBOs that will create an account with username/password, but then have to pass the user on to the login page to login.  Would be much nicer to create the account and log them in one step, instead of two.

I am trying to create a cookie using the masterpages.  The site that reads the cookie doesn't see it.  They are both in the same domain.  I am creating the cookie in the load event.  The  cookie isn't being created.  Here is my code:

HttpCookie aCookie = new HttpCookie("DDPASecurity");

aCookie.Values["Auth"]="user@domain.com";

Integrating Third Party .Net website with iMIS through Unified Login

My organization wants me to application forms to our website and secure them with iMIS authentication.  We decided to integrate through unified login so we could use iMIS public view for Events Registration and account creation to avoid reinventing the wheel.

This however requires that I identify users detail after login.