Hi Anmol, You can set the Expires header to 0 on the initial Register request – this will mean that Bono won’t store a flow token for the registration request (so any future requests will be re-authenticated).
Ellie From: Anmol Garg [mailto:[email protected]] Sent: 26 March 2015 19:32 To: Eleanor Merry Cc: clearwater Subject: Re: [Clearwater] Fwd: Clear HSS data after registration Hi Eleanor, Thanks for the above information. In addition to the information in my previous mail, if I send the registration request immediately or within a specific time period then it sends me a 200 OK response immediately. On the contrary if I send the request after some significant time then it goes through the entire process again, so I am guessing it must be because of some caching. Therefor is there a way to do this inside the Clearwater infrastructure itself instead of using the client to send such a request for each user. Something like deleting a file, changing some cache ttl parameter in a configuration file or a reset command. Any help on these lines will be very helpful. Thank you in advance. Regards Anmol On Fri, Mar 27, 2015 at 12:30 AM, Eleanor Merry <[email protected]<mailto:[email protected]>> wrote: Hi Anmol, You can achieve this by deregistering the client (i.e. send a REGISTER with an Expires header set to 0). Hope this helps, Ellie -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Anmol Garg Sent: 25 March 2015 14:23 To: clearwater Subject: [Clearwater] Fwd: Clear HSS data after registration Dear All, As a part of my Bachelor Thesis, I am trying to benchmark project clearwater for registration requests. As of now I am using only a single node for each component. The installation is done using the manual install method from the docs. I have also made a client which sends registration requests to the system as "[email protected]<mailto:[email protected]>" to "[email protected]<mailto:[email protected]>" when X registration requests are sent at a particular rate. Currently when I register a user for the first time, I first get an unauthorized response for which my client sends a re-request and I finally get a 200 OK response for the user which suggests that my user has been registered successfully. But now if I resend the re-register the same user, I directly get a 200 OK response back. On the contrary, what I want to do is go through the entire process of first getting an unauthorized response followed by a re-request and then finally a 200 OK response. Can you please help me how to solve this? Basically, what I want to do is clear the registration data stored in the HSS for the registered users so that I can start afresh even when I register the same user again. Looking forward to your response. Regards Anmol Garg Senior Undergrad CSE IIT Bombay _______________________________________________ Clearwater mailing list [email protected]<mailto:[email protected]> http://lists.projectclearwater.org/listinfo/clearwater -- Anmol Garg | Junior Undergraduate | CSE, IIT Bombay | Internship Coordinator, CSE _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
