Wal*_*ena 18 authentication nsurlcredential ios swift alamofire
使用Basic Auth进行身份验证时遇到问题.我正在使用符合URLRequestConvertible
协议的标准枚举来构造我的请求.问题是,当我在枚举中手动设置授权标头时,如下所示:
let user = ***
let password = ***
let credentialData = "\(user):\(password)".dataUsingEncoding(NSUTF8StringEncoding)!
let base64Credentials = credentialData.base64EncodedStringWithOptions([])
mutableURLRequest.setValue("Basic \(base64Credentials)", forHTTPHeaderField: "Authorization")
Run Code Online (Sandbox Code Playgroud)
我总是得到401未经授权的回复.但是,如果我使用authenticate
回调设置密码,如下所示:
Alamofire.request(request)
.authenticate(user: "USERNAME_HERE", password: "PASSWORD_HERE")
.responseJSON { (response) -> Void in
print("JSON response \(response)")
completion(success: true, error: nil)
}
Run Code Online (Sandbox Code Playgroud)
它正确验证.我希望能够在enum中手动设置它,URLRequestConvertible
而不是传入凭据authenticate
.
我知道它正在使用NSURLCredential
引擎盖来进行auth挑战,但我希望能够手动设置它.
这是我的URLRequestConvertible
实现:
enum CheckedUpAPI: URLRequestConvertible {
static let baseURLString = "https://***"
static let APIKey = "***"
static let APIClientName = "iPad"
case UpdatePatient(String, [String: AnyObject])
var method: Alamofire.Method {
switch self {
case .UpdatePatient:
return .PATCH
}
}
var path: String {
switch self {
case .UpdatePatient(let patientID, _):
return "patients/\(patientID)"
}
}
// MARK: URLRequestConvertible
var URLRequest: NSMutableURLRequest {
let URL = NSURL(string: CheckedUpAPI.baseURLString)!
let mutableURLRequest = NSMutableURLRequest(URL: URL.URLByAppendingPathComponent(path))
mutableURLRequest.HTTPMethod = method.rawValue
/**
We are not setting any authorization headers since they requests return 401
the `authenticate` function on Alamofire.request does the trick
let user = "easy@test.com"
let password = "test"
let credentialData = "\(user):\(password)".dataUsingEncoding(NSUTF8StringEncoding)!
let base64Credentials = credentialData.base64EncodedStringWithOptions([])
mutableURLRequest.setValue("Basic \(base64Credentials)", forHTTPHeaderField: "Authorization")
*/
mutableURLRequest.setValue(CheckedUpAPI.APIKey, forHTTPHeaderField: "API-Key")
switch self {
case .UpdatePatient(_, let parameters):
return Alamofire.ParameterEncoding.JSON.encode(mutableURLRequest, parameters: parameters).0
}
}
}
Run Code Online (Sandbox Code Playgroud)
be.*_*esh 24
在swift 3.0中
使用以下代码 -
let user = ***
let password = ***
let credentialData = "\(user):\(password)".data(using: String.Encoding.utf8)!
let base64Credentials = credentialData.base64EncodedString(options: [])
let headers = ["Authorization": "Basic \(base64Credentials)"]
Alamofire.request(customerURL,
method: .get,
parameters: nil,
encoding: URLEncoding.default,
headers:headers)
.validate()
.responseJSON { response in
if response.result.value != nil{
print(response)
}else{
}
}
Run Code Online (Sandbox Code Playgroud)
小智 18
Alamofire.request(urlString, method: .get).authenticate(user: "username", password: "pwd").responseJSON
Run Code Online (Sandbox Code Playgroud)
只是认证
小智 14
你可以试试这段代码:
let user = ***
let password = ***
let credentialData = "\(user):\(password)".dataUsingEncoding(NSUTF8StringEncoding)!
let base64Credentials = credentialData.base64EncodedStringWithOptions([])
let headers = ["Authorization": "Basic \(base64Credentials)"]
Alamofire.manager.request(.GET, stringURL,headers: headers, parameters: params as? [String : AnyObject])
.responseJSON { response in
if (response.result.error == nil){
success(data: response.result.value)
}else{
fail(error: response.result.error)
}
}
Run Code Online (Sandbox Code Playgroud)
小智 6
斯威夫特 4
private func getHeaders() -> [String: String] {
let userName = "xxxx"
let password = "xxxx"
let credentialData = "\(userName):\(password)".data(using: .utf8)
guard let cred = credentialData else { return ["" : ""] }
let base64Credentials = cred.base64EncodedData(options: [])
guard let base64Date = Data(base64Encoded: base64Credentials) else { return ["" : ""] }
return ["Authorization": "Basic \(base64Date.base64EncodedString())"]
}
Run Code Online (Sandbox Code Playgroud)
最终明白了问题所在。结果是 URL 中缺少尾部正斜杠。看来 Alamofire 的处理方式与 AFNetworking 的处理方式不同。我能够弄清楚记录请求并发现我们在实际请求中丢失了一些字节。
归档时间: |
|
查看次数: |
17070 次 |
最近记录: |