using a single sql membership for 2 web applications

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Andy B

    using a single sql membership for 2 web applications

    I have 2 web applications that need membership added to them. 1 is an admin
    module for the admin to control the website and the other one is contracts
    module where customers/clients can login and manage their contracts. I want
    to use 1 centeralized membership provider and database for the usernames and
    passwords but don't want clients/customers to have access to the admin
    module. How would I do something like this?


  • Cowboy \(Gregory A. Beamer\)

    #2
    Re: using a single sql membership for 2 web applications

    Create it in one site and then copy the ConnectionStrin gs and Membership
    (possible Roles and Personalization ) sections to the web.config in the other
    application. You should also consider generating your own machine keys and
    use the same settings in both applications (there are sites you can google
    that will gen random keys for you).

    --
    Gregory A. Beamer
    MVP, MCP: +I, SE, SD, DBA

    Subscribe to my blog


    or just read it:


    *************** *************** **************
    | Think outside the box! |
    *************** *************** **************
    "Andy B" <a_borka@sbcglo bal.netwrote in message
    news:e5Qh%234x1 IHA.4704@TK2MSF TNGP05.phx.gbl. ..
    >I have 2 web applications that need membership added to them. 1 is an admin
    >module for the admin to control the website and the other one is contracts
    >module where customers/clients can login and manage their contracts. I want
    >to use 1 centeralized membership provider and database for the usernames
    >and passwords but don't want clients/customers to have access to the admin
    >module. How would I do something like this?
    >

    Comment

    • Andy B

      #3
      Re: using a single sql membership for 2 web applications

      How would you do this? I don't know if I can use machine keys or not since I
      am making the site on a different computer than the server.


      "Cowboy (Gregory A. Beamer)" <NoSpamMgbworld @comcast.netNoS pamMwrote in
      message news:eaPrWXz1IH A.4912@TK2MSFTN GP03.phx.gbl...
      Create it in one site and then copy the ConnectionStrin gs and Membership
      (possible Roles and Personalization ) sections to the web.config in the
      other application. You should also consider generating your own machine
      keys and use the same settings in both applications (there are sites you
      can google that will gen random keys for you).
      >
      --
      Gregory A. Beamer
      MVP, MCP: +I, SE, SD, DBA
      >
      Subscribe to my blog

      >
      or just read it:

      >
      *************** *************** **************
      | Think outside the box! |
      *************** *************** **************
      "Andy B" <a_borka@sbcglo bal.netwrote in message
      news:e5Qh%234x1 IHA.4704@TK2MSF TNGP05.phx.gbl. ..
      >>I have 2 web applications that need membership added to them. 1 is an
      >>admin module for the admin to control the website and the other one is
      >>contracts module where customers/clients can login and manage their
      >>contracts. I want to use 1 centeralized membership provider and database
      >>for the usernames and passwords but don't want clients/customers to have
      >>access to the admin module. How would I do something like this?
      >>
      >

      Comment

      • sloan

        #4
        Re: using a single sql membership for 2 web applications


        You need to look at the RolesProvider (kind of an "add on" to the
        MembershipProvi der).

        I would then try to tie it into a sitemap.



        That's a starter hint anyways.




        "Andy B" <a_borka@sbcglo bal.netwrote in message
        news:e5Qh%234x1 IHA.4704@TK2MSF TNGP05.phx.gbl. ..
        >I have 2 web applications that need membership added to them. 1 is an admin
        >module for the admin to control the website and the other one is contracts
        >module where customers/clients can login and manage their contracts. I want
        >to use 1 centeralized membership provider and database for the usernames
        >and passwords but don't want clients/customers to have access to the admin
        >module. How would I do something like this?
        >

        Comment

        Working...