Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Web Development
  3. ASP.NET
  4. Webservice security design

Webservice security design

Scheduled Pinned Locked Moved ASP.NET
csharpdesignsysadminsecurityarchitecture
1 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • V Offline
    V Offline
    Vecta
    wrote on last edited by
    #1

    I'm hoping someone here can help me, I'm developing a webservice in c# for a legacy system with a fairly fixed architecture. The way its "security" works is that once an initial username/password pair is validated it returns a session ID (a sequential one) and all subsequent requests just require that ID. I've been looking at ws-security and ws-trust, I can manage a secure transaction on the initial login request but once that is done I'm unsure how to securely manage passing around this session ID, I was thinking of caching the "real" session ID in a hashtable on the server and returning a more secure ID to the client. Is this is good idea or are there better / more standard ways of doing this? Thanks Ric.

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups