guys,
do you have any idea on the topic??

I am now using cisco WLC with local net user as a web based authentication for wifi users. also i can do the user account lifetime and after that, the account gets deleted. But now i am using proxy and also has a plan of using wccp. in this case, the wifi users first have to get the wlc page for auth. then they can go net. now as browser is with proxy, it actually can not open the page. I have tried to exclude the wlc ip but no work. now in the case if i use a external web form with ldap, i hope it will be solved. but again, so far, i found ldap users remain. where i wish them to be deleted after lifetime. so guys, can somebody help?? some link for study may be...

Mishu~

if there is config in the WLC that references the users, then that's clearly nothing to do with Linux at all, you should raise a TAC case with cisco to clarify anything there. In terms of making the account unusable, then you should just set an password expiration time on the server, and then regardless of the WLC config, it will not be able to bind to LDAP with that account.

no no... it was not like that...

I have a working WLC. things are fine... and right now I can easily get what I want... but this way I dont... in cisco, we can use the lobby ambassador to open guest accounts (as local net users) (also i made a VB app that uses the telnet to do the same). Every guest accounts has a life time (what ever we set) and after that, it gets deleted. This is what exactly I want... but not using Cisco's local net users. Instead, I wish to use the AAA for this job.

So when a guest wish to have access, my men can add the account for that amount of life time and then guest can get wifi access (wlc can work with AAA). And after the time finished of the account, the account should be deleted automatically...

Now this part I wish to do using linux and thus I am looking for the ans... otherwise, Cisco's current technology is fine... but as I said, I dont want to use that...

Mishu~

Well you won't have ldap deleting its own data. You would script that somehow. Maybe use an 'at' task if you really must delete the account. This seems an odd thing to want to do though if you can just use an account expiry attribute.